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 agentmods add skills/sonichi/sutando/agent-registrynpx skills add sonichi/sutando --skill agent-registrygit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/agent-registry)<a href="https://agentmods.dev/skills/sonichi/sutando/agent-registry"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/agent-registry.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.01092 |
| Opus 5 | $0.00033 | $0.00546 |
| Sonnet 5 | $0.00013 | $0.00218 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
agent-registry 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Registry
A thin local service that tracks running agent instances. Claude Code instances register themselves on startup (via a SessionStart hook) and heartbeat while alive; consumers read the live list over a localhost HTTP API.
This is not the AG2 Workforce Hub app. It is a small local service that can
optionally mirror its state to an AG2 hub using the hub connection layer
(ag2_workforce.hub.client) — see "Optional: AG2 Hub mirroring" below — but the
core service has zero third-party dependencies and works entirely offline.
Components
skills/agent-registry/
├── scripts/registry-service.py # the HTTP service + SQLite store
├── scripts/registry-client.py # CLI: register / heartbeat / deregister / list / watch
└── hooks/session-start.sh # Claude Code SessionStart hook
- DB:
<workspace>/data/agent-registry.db(SQLite, auto-created) - Discovery file:
<workspace>/state/agent-registry.json— written by the service with the bound port so clients find it without a hardcoded port. - Port: binds
127.0.0.1, first free port from7847upward.
Running the service
It is startable by Sutando three ways, in order of preference:
- Auto-start (default). Any
registry-client.pycall with--autostartlaunches the service detached if it is not already running. The SessionStart hook passes--autostart, so the first Claude Code session to start brings the registry up. - From
startup.sh. For an always-on registry, add tosrc/startup.sh:python3 skills/agent-registry/scripts/registry-service.py & - By hand:
python3 skills/agent-registry/scripts/registry-service.py
Registering Claude Code instances
Add the SessionStart hook to .claude/settings.json:
{
"hooks": {
"SessionStart": [
{ "hooks": [
{ "type": "command",
"command": "bash skills/agent-registry/hooks/session-start.sh" }
] }
]
}
}
On session start the hook backgrounds registry-client.py watch, which
registers the instance, heartbeats every 30s, and deregisters when the session
ends. If it is killed ungracefully the entry ages out via heartbeat staleness
(> 90s → stale; stopped/stale rows are pruned after 1h).
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 103 lines · 66 tokens per session scan A 2028192981c9
agent-registry is a skill published in the GitHub repository sonichi/sutando (391 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,092 once invoked, about $0.0003 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-30.
Other skills, from other repositories
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
contacts
Manage contacts, communication channels, access control, and invite links.
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).