Add @jonathanbulkeley/plugin-mycelia-signal

[jonathanbulkeley]

Mycelia Signal sovereign price oracle plugin for ElizaOS.

• 56 endpoints: crypto pairs, FX rates, economic indicators, commodities
• Pay per query via Lightning (L402, secp256k1 ECDSA) or USDC on Base (x402, Ed25519)
• npm: https://www.npmjs.com/package/@jonathanbulkeley/plugin-mycelia-signal
• Docs: https://myceliasignal.com/docs

Summary by CodeRabbit

• Chores
  • Registered a new plugin in the available plugins index, expanding the plugin ecosystem and making it accessible for users.

Greptile Summary

This PR adds @jonathanbulkeley/plugin-mycelia-signal to the plugin registry — a sovereign price oracle plugin providing crypto, FX, commodities, and economic indicator data via Lightning/USDC payments.

• The GitHub repository (jonathanbulkeley/elizaos-plugin-mycelia-signal) exists and is publicly accessible
• Alphabetical sorting violation: The new entry is inserted after @kudo-dev/plugin-kudo (line 229) but should be placed after @esscrypt/plugin-polkadot (line 226), since @jonathanbulkeley sorts before @kamiyo and @kudo-dev
• This will likely fail the CI alphabetical sorting check

Confidence Score: 2/5

• This PR requires a minor fix to alphabetical ordering before merging.
• The new plugin entry is valid (GitHub repo exists, format is correct), but it violates the required alphabetical sorting convention. This is a straightforward fix — the entry just needs to be moved up a few lines.
• index.json — the new entry on line 229 needs to be moved to line 227 (after @esscrypt/plugin-polkadot) to maintain alphabetical order.

Important Files Changed

Filename	Overview
index.json	New plugin entry added but placed in incorrect alphabetical position. @jonathanbulkeley/plugin-mycelia-signal is after @kudo-dev/plugin-kudo but should be after @esscrypt/plugin-polkadot (j < k). GitHub repo exists and is accessible.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["PR: Add plugin entry to index.json"] --> B["index.json updated"]
    B --> C["CI: Validate JSON format ✅"]
    B --> D["CI: Check alphabetical sort ❌"]
    B --> E["CI: Verify GitHub repo exists ✅"]
    B --> F["CI: Verify NPM package exists"]
    D --> G["Entry @jonathanbulkeley/plugin-mycelia-signal\nis after @kudo-dev but should be before @kamiyo"]
    G --> H["Fix: Move entry to correct position\n(after @esscrypt/plugin-polkadot)"]
    H --> I["Auto-generate registry on merge"]
    I --> J["generated-registry.json updated"]

Loading

_{Last reviewed commit: a41db20}

Greptile also left 1 inline comment on this PR.

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

[coderabbitai]

Walkthrough

A new plugin mapping for @jonathanbulkeley/plugin-mycelia-signal pointing to github:jonathanbulkeley/elizaos-plugin-mycelia-signal is added to the public plugin index in index.json.

Changes

Cohort / File(s)	Summary
Plugin Registry Update index.json	Added new plugin entry mapping @jonathanbulkeley/plugin-mycelia-signal to its GitHub repository location.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A signal blooms in mycelia's call,
Through plugin paths we add it all,
Jonathan's gift in code we trust,
Another node feeds plugin dust! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description lacks the required Registry Update Checklist template, making it impossible to verify compliance with mandatory requirements like alphabetical sorting, JSON validity, and plugin repo standards.	Add the Registry Update Checklist from the template to the PR description and ensure all items (especially alphabetical ordering) are addressed before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the new plugin being added to the registry, directly matching the main change in the changeset.
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

📝 Coding Plan

• Generate coding plan for human review comments

---

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.}

[greptile-apps]

Entry is not in alphabetical order. The entry @jonathanbulkeley/plugin-mycelia-signal is currently placed after @kudo-dev/plugin-kudo, but alphabetically j < k, so it should appear before @kamiyo/eliza (after @esscrypt/plugin-polkadot on line 226). Please move it to maintain the required alphabetical sorting.

Suggested change

	"@jonathanbulkeley/plugin-mycelia-signal": "github:jonathanbulkeley/elizaos-plugin-mycelia-signal",
	"@mascotai/plugin-connections": "github:mascotai/plugin-connections",

[coderabbitai]

🧹 Nitpick comments (1)

index.json (1)

227-230: Keep plugin keys alphabetically ordered around the new entry.

Line 229 adds the correct mapping, but its position breaks the local sort order (@jonathan... should be before @kamiyo.../@kudo...). Reordering keeps diffs predictable and reduces future merge churn.

♻️ Proposed reorder

-   "@kamiyo/eliza": "github:kamiyo-ai/kamiyo-protocol#main:packages/kamiyo-eliza",
-   "@kudo-dev/plugin-kudo": "github:Kudo-Archi/plugin-kudo",
    "@jonathanbulkeley/plugin-mycelia-signal": "github:jonathanbulkeley/elizaos-plugin-mycelia-signal",
+   "@kamiyo/eliza": "github:kamiyo-ai/kamiyo-protocol#main:packages/kamiyo-eliza",
+   "@kudo-dev/plugin-kudo": "github:Kudo-Archi/plugin-kudo",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@index.json` around lines 227 - 230, The plugin mapping entries in index.json
are out of alphabetical order; move the
"@jonathanbulkeley/plugin-mycelia-signal":
"github:jonathanbulkeley/elizaos-plugin-mycelia-signal" entry so it appears
before "@kamiyo/eliza" and "@kudo-dev/plugin-kudo" to restore local alphabetical
order of keys; ensure the surrounding plugin keys remain unchanged and that
commas/JSON formatting are preserved after the reorder.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@index.json`:
- Around line 227-230: The plugin mapping entries in index.json are out of
alphabetical order; move the "@jonathanbulkeley/plugin-mycelia-signal":
"github:jonathanbulkeley/elizaos-plugin-mycelia-signal" entry so it appears
before "@kamiyo/eliza" and "@kudo-dev/plugin-kudo" to restore local alphabetical
order of keys; ensure the surrounding plugin keys remain unchanged and that
commas/JSON formatting are preserved after the reorder.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 24d34645-01c7-4808-9173-e4001e21c2ab

📥 Commits

Reviewing files that changed from the base of the PR and between ef4930f and a41db20.

📒 Files selected for processing (1)

• index.json