Add eliza-plugin-supercolony

[randomblocker]

Adds eliza-plugin-supercolony to the plugin registry.

What it does: Gives Eliza agents access to real-time intelligence from 140+ autonomous AI agents on the Demos blockchain. 4 actions: feed reading, search, consensus signals, and network stats.

npm: eliza-plugin-supercolony (v0.1.5)
GitHub: TheSuperColony/eliza-plugin-supercolony

Summary by CodeRabbit

• Style
  • Updated formatting for improved readability with no functional changes.

Greptile Summary

This PR adds eliza-plugin-supercolony to the ElizaOS plugin registry, pointing to github:TheSuperColony/eliza-plugin-supercolony. The plugin provides Eliza agents with real-time intelligence from 140+ autonomous AI agents on the Demos blockchain via 4 actions (feed reading, search, consensus signals, and network stats).

• The new registry entry ("eliza-plugin-supercolony": "github:TheSuperColony/eliza-plugin-supercolony") is correctly placed alphabetically within the unscoped entries section and follows the same github: reference format used by all other entries.
• The entire file has been reformatted from 3-space to 2-space indentation as part of this PR. This is an unrelated change that adds noise to the diff and is likely to cause merge conflicts with other open PRs modifying index.json. The indentation change should be reverted so only the new entry is added.

Confidence Score: 3/5

• Safe to merge after reverting the unnecessary whole-file indentation change.
• The new plugin entry itself is valid and well-formed, but the PR inadvertently reformats all 244 existing entries from 3-space to 2-space indentation, which is unrelated to the intended change and will generate merge conflicts with other open PRs targeting the same file.
• index.json — the whole-file indentation change needs to be reverted.

Important Files Changed

Filename	Overview
index.json	Adds eliza-plugin-supercolony entry pointing to github:TheSuperColony/eliza-plugin-supercolony. The new entry itself is correctly placed and follows the unscoped naming convention used by other entries. However, the entire file has been reformatted from 3-space to 2-space indentation, which is an unrelated and unnecessary change that will create merge conflicts with other open PRs.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[ElizaOS Agent] -->|loads plugin| B[eliza-plugin-supercolony]
    B --> C[Feed Reading]
    B --> D[Search]
    B --> E[Consensus Signals]
    B --> F[Network Stats]
    C & D & E & F -->|queries| G[Demos Blockchain\n140+ Autonomous AI Agents]
    G -->|real-time intelligence| B

Loading

Comments Outside Diff (1)

1. index.json, line 249-491 (link)

   Unnecessary whole-file indentation change

   This PR reformats every single entry in index.json from 3-space indentation to 2-space indentation. The only intended change is adding eliza-plugin-supercolony, but the diff shows all 244 existing entries have been re-indented. This adds significant noise to the diff, makes it harder to review the actual new entry, and is likely to cause merge conflicts with other open PRs that are also adding entries to this file.

   Please revert the indentation change and only add the new entry, preserving the existing 3-space indentation style used throughout the file.

_{Last reviewed commit: 39f2538}

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

[coderabbitai]

Walkthrough

The pull request applies formatting and whitespace adjustments to index.json. All data mappings remain semantically identical with no functional modifications or changes to exported declarations.

Changes

Cohort / File(s)	Summary
JSON Formatting index.json	Whitespace and indentation adjustments; no functional or semantic changes to data mappings.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through JSON neat,
Formatting spaces, oh so sweet!
Indents aligned in perfect rows,
Where beauty in white spacing flows. 🐰✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description lacks the required checklist items from the Registry Update Checklist template, particularly verification items for NPM naming, alphabetical placement, JSON validity, and plugin repo requirements.	Add a completed Registry Update Checklist to the PR description, confirming all required items are met (NPM naming, alphabetical placement, JSON validity, plugin repo accessibility, main branch, topics, images, and agentConfig in package.json).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a new plugin to the registry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}