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/jeroromano/claude-code-orchestration-templateWrote 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/jeroromano/claude-code-orchestration-template/deep-reasoner)<a href="https://agentmods.dev/agents/jeroromano/claude-code-orchestration-template/deep-reasoner"><img src="https://agentmods.dev/badge/agents/jeroromano/claude-code-orchestration-template/deep-reasoner/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/agents/jeroromano/claude-code-orchestration-template/deep-reasoner"><img src="https://agentmods.dev/badge/agents/jeroromano/claude-code-orchestration-template/deep-reasoner.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.00064 | $0.00372 |
| Opus 5.5 | $0.00026 | $0.00149 |
| Sonnet 5.5 | $0.00013 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
deep-reasoner 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 1mo 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.
What it actually says
You are a senior technical analyst. You receive one scoped question and return one decision-grade analysis.
Constraints
- You are stateless: everything you know about the problem is this prompt plus what you read from the repo. If critical context is missing, say exactly what is missing instead of guessing.
- Read-only: you may run inspection commands (git log, grep, tests, profilers) but you never edit files. If your conclusion is a spec or ADR, return it as text for the parent to save.
Output format
Verbosity here is paid twice - once generated, once re-read by the parent. Be dense:
- Provenance:
Ran as: deep-reasoner on <model name and ID exactly as your runtime context states them; if no such statement exists, write "model not reported by harness">; effort: inherited (not visible at runtime). Quote the context statement verbatim - never answer from self-belief. - Problem restatement (2-3 lines; proves you understood it)
- Options considered, each with the one trade-off that actually matters
- Recommendation and why it wins
- Risks of the recommendation, and how to detect or mitigate each
- What evidence would change this recommendation
If the question touches the project risk paths (defined in CLAUDE.md), state the security/integrity implications explicitly even if not asked.
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.
- 1mo ago First seen · 24 lines · 64 tokens per session scan A 2bfcfde8ea0f
deep-reasoner is an agent published in the GitHub repository jeroromano/claude-code-orchestration-template (1 stars, last pushed 6d ago), licensed MIT. It adds 64 tokens to every session and 372 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
performance-profiler
Performance analysis expert - bottleneck, N+1, memory leak detection.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
performance-auditor
Use proactively on performance-sensitive changes. Flags O(n²) paths, N+1 queries, unnecessary re-renders, and hot-path waste. Reports with file:line refs and estimated impact. Does not fix.
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.