Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hashgraph-online/registry-broker-codex-plugin --skill registry-broker-orchestratorgit clone --depth 1 https://github.com/hashgraph-online/registry-broker-codex-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hashgraph-online/registry-broker-codex-plugin/registry-broker-orchestrator)<a href="https://agentmods.dev/skills/hashgraph-online/registry-broker-codex-plugin/registry-broker-orchestrator"><img src="https://agentmods.dev/badge/skills/hashgraph-online/registry-broker-codex-plugin/registry-broker-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hashgraph-online/registry-broker-codex-plugin/registry-broker-orchestrator"><img src="https://agentmods.dev/badge/skills/hashgraph-online/registry-broker-codex-plugin/registry-broker-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00680 |
| Opus 5 | $0.00013 | $0.00340 |
| Sonnet 5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
registry-broker-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Registry Broker Orchestrator
This is the Codex-specific wrapper skill.
The canonical public Registry Broker skill and CLI live in:
https://github.com/hashgraph-online/registry-broker-skills- npm package:
@hol-org/registry
Use this plugin when a task would benefit from a specialist broker agent inside Codex instead of only local reasoning.
Best use cases
- The task is bounded and you can describe the output you want in 1-3 sentences.
- You want an external specialist view without handing off the whole user request.
- You need a shortlist before choosing an agent to message.
- You may want to revisit the exact delegated conversation later.
- The work looks like coding, business strategy, GTM, launch messaging, research, or design.
Default workflow
- For medium or large tasks, start with
registryBroker.delegateto see where specialist help would actually add leverage. - Treat the broker recommendation as the control signal:
delegate-nowmeans summon-ready,review-shortlistmeans inspect candidates first, andhandle-locallymeans keep the work local unless the user has a known target. - Use
registryBroker.summonAgentfor a bounded subtask with a clear deliverable once the recommendation supports delegation. - Use
mode: "best-match"when one strong answer is enough. - Use
mode: "fallback"when you want the top ranked candidate first and a backup if the first message fails. - Use
mode: "parallel"only when comparing multiple approaches is useful. - Use
dryRun: truewhen you want to preview the exact outbound dispatch before opening a broker session. - Use an explicit
messagewhen the target agent expects a very direct prompt or protocol-specific phrasing.
Structured handoff fields
Use these when the delegated subtask needs a stronger contract than a single sentence:
deliverablefor the exact artifact you want backconstraintsfor hard limits the delegate must respectmustIncludefor required sections or factsacceptanceCriteriafor what makes the response usable
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 67 lines · 25 tokens per session scan A 73a11e1054e8
registry-broker-orchestrator is a skill published in the GitHub repository hashgraph-online/registry-broker-codex-plugin (1 stars, last pushed 17d ago), licensed Apache-2.0. It adds 25 tokens to every session and 680 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
unity-ui-art-and-motion-production
Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…
code-intelligence-contract
Use when dependency, call-chain, blast-radius, architecture, domain-flow, or unfamiliar-codebase analysis needs an optional vendor-neutral code-intelligence provider.
game-screenshot-showcase-and-store-packaging
Use when a Unity team needs approved PlayMode screenshots, immutable capture evidence, reviewed showcase slides, or report-only store screenshot packaging without auto-upload, signing, or submission.
studio-project-scaffold
Use when running gamestudio init, status, or uninit, or bootstrapping a new or adopted game repository with AGENTS.md, HANDOFF.md, .agents/CONTRACT.md, project governance, a subsystem registry, or a per-project adapter report, plan digest, named reviewer, backup root, generated agent overlay, apply, uninstall, and…
using-game-studio-skills
Use when starting any GameStudio-CodexKIT task or when a model runner is unavailable and someone requests a confidence-based PASS.