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 daddia/claude-for-strategy --skill registry-browsergit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/registry-browser)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/registry-browser"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/registry-browser/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/daddia/claude-for-strategy/registry-browser"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/registry-browser.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.00065 | $0.00894 |
| Opus 5 | $0.00032 | $0.00447 |
| Sonnet 5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
registry-browser 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 6d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/strategy-builder-hub:registry-browser
When to use
Search watched registries; preview full SKILL.md; add registries to watchlist on confirmation.
Preconditions
| Input | If missing |
|---|---|
| Hub profile with watched registries | Offer to add registry or practice-setup |
Provisional mode
Empty watchlist — guide user to add first trusted registry.
Trust spine
Structured-aggregation; browse only — no install without skill-installer.
Workflow
Find skills across the watched registries. Search, preview, decide.
Load context
~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/CLAUDE.md → watched registries list.
Workflow
Step 1: Fetch registry indexes
For each watched registry:
- GitHub repos: fetch
skills/directory listing and eachSKILL.mdfrontmatter (name + description). - Marketplace-style registries: fetch the index.
Cache the index locally (references/registry-cache.json) so browsing is fast. Refresh cache if >7 days old or on request.
Step 2: Search
Match query against skill names and descriptions. Simple keyword match is fine — these are small enough that fuzzy search is overkill.
Also: browse by category if the registry organizes skills that way.
Step 3: Present matches
## Search: "[query]"
**Found [N] skills across [M] registries:**
### [skill-name]
**From:** [registry name]
**Description:** [from frontmatter]
[View full SKILL.md] [Install]
### [skill-name]
[...]
Step 4: Preview
On "view full SKILL.md": fetch and show the whole file. User reads it before deciding to install. No surprises.
Step 5: Add a registry
If the user has a URL to a registry not in the watchlist:
- Fetch it, validate it's a skills repo (has
skills/or.claude-plugin/) - Show what's in it
- Add to
~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/CLAUDE.md→ watched registries on confirmation
Default registries
No default registries are pre-configured. Add registries you trust via this command or by editing your engagement profile directly.
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.
- 6d ago First seen · 115 lines · 65 tokens per session scan A 4b1f17df0d42
registry-browser is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 894 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-09-03.
Other skills, from other repositories
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
spec-herdr-review
Run visible multi-agent spec reviews in Herdr through interactive agent CLIs such as Claude, Codex, Copilot/GLM, or Grok/Composer. Supports two modes — a spec review (the design, before implementation) and an implementation review (the implemented diff vs the spec, after the calling model has built it). Ask for…
gpmc
Read-only Active Directory Group Policy inventory via LDAP — list GPOs, show OU/site links (enabled/disabled/enforced), find unlinked GPOs, search by name, and gpresult for the current user. Use when the user asks about GPOs, Group Policy, GPMC, linked vs unlinked policies, RSoP, what applies to this user, or runs…
grok-session
Find and inspect local Grok CLI conversations by session GUID, title, phrase, or recent activity. Use when the user runs /grok-session, asks what Grok work they have been doing lately, says a Grok conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named session, or wants to continue…
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…
codex-session
Find and inspect local Codex task conversations, including by session GUID, title, recent activity, or a phrase from the conversation. Use when the user runs /codex-session, says a prior Codex conversation died or ran out of context, wants to resume a named task, asks what a local Codex task did, or wants to continue…