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.
git clone --depth 1 https://github.com/asleekgeek/claude-multiagent-catalogueWrote 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/agents/asleekgeek/claude-multiagent-catalogue/implementation-plan)<a href="https://agentmods.dev/agents/asleekgeek/claude-multiagent-catalogue/implementation-plan"><img src="https://agentmods.dev/badge/agents/asleekgeek/claude-multiagent-catalogue/implementation-plan.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.1 | $0.00016 | $0.01441 |
| Opus 5 | $0.00008 | $0.00720 |
| Sonnet 5 | $0.00003 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
implementation-plan 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 164 lines · 16 tokens per session scan A 2dcfb65e656e
implementation-plan is an agent published in the GitHub repository asleekgeek/claude-multiagent-catalogue (2 stars, last pushed 3mo ago), with no licence file. It adds 16 tokens to every session and 1,441 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-09-03.
Other agents, from other repositories
RPI Planner
Planning subagent for the RPI Orchestrator. Creates actionable implementation plans grounded in research findings and codebase conventions.
RPI Implementor
Implementation subagent for the RPI Orchestrator. Executes one or more implementation phases from an approved plan with full codebase access and change tracking.
RPI Researcher
Research subagent for the RPI Orchestrator. Investigates codebase, documentation, and external sources to produce consolidated research findings for a given task.
RPI Reviewer
Review subagent for the RPI Orchestrator. Validates completed implementation against the plan and research, producing severity-graded findings.
sql-developer
Use this agent when the user explicitly requests help with SQL Server or T-SQL development tasks. This includes writing queries, creating stored procedures, optimizing performance, analyzing execution plans, or reviewing SQL code. Context: User is starting a new database project and needs help with queries. user…
swift-developer
Use this agent when the user explicitly requests help with Swift, iOS, or macOS development tasks. This includes building Swift packages, creating iOS/macOS apps, implementing SwiftUI views, working with Swift 6 concurrency, running xcodebuild commands, or reviewing Swift code. Context: User is starting a new iOS…