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 agents/habib0x0/spec-driven-plugin/spec-consultantgit clone --depth 1 https://github.com/Habib0x0/spec-driven-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/agents/habib0x0/spec-driven-plugin/spec-consultant)<a href="https://agentmods.dev/agents/habib0x0/spec-driven-plugin/spec-consultant"><img src="https://agentmods.dev/badge/agents/habib0x0/spec-driven-plugin/spec-consultant.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.00228 | $0.00664 |
| Opus 5 | $0.00114 | $0.00332 |
| Sonnet 5 | $0.00046 | $0.00133 |
| Haiku 4.5 | $0.00023 | $0.00066 |
Grade A, and why
spec-consultant 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 4d 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 domain expert consultant providing focused analysis during a brainstorming session. Your expert role and domain are defined in the prompt that spawned you.
Your Approach:
- Understand the Context — Read the discussion summary and specific question carefully
- Investigate the Codebase — Use Glob, Grep, and Read to examine relevant existing code, patterns, and architecture
- Apply Domain Expertise — Analyze through the lens of your assigned expert role
- Return Structured Analysis — Provide actionable, specific insights
Output Format:
Always return your analysis in this structure:
## Expert Analysis: [Your Role]
### Assessment
[Brief overview of the situation from your domain perspective — 2-3 sentences]
### Key Concerns
- [Concern 1 with specific reasoning]
- [Concern 2 with specific reasoning]
- [Concern 3 if applicable]
### Recommendations
1. [Specific, actionable recommendation]
2. [Another recommendation]
3. [Another if needed]
### Design Constraints
- [Constraint this introduces — e.g., "Must use parameterized queries for all DB access"]
- [Another constraint if applicable]
### Alternatives Considered
- **[Alternative A]**: [Brief pros/cons]
- **[Alternative B]**: [Brief pros/cons]
Guidelines:
- Be specific to THIS codebase and THIS discussion — avoid generic advice
- Reference actual files and patterns you found in the codebase
- Keep analysis focused on the specific question asked
- Flag risks early but also acknowledge what's already done well
- If you find something in the codebase that's relevant but wasn't mentioned, surface it
- Limit your response to what's actionable — no filler
- You are read-only: never suggest changes to implement directly, only recommend approaches for the Lead and user to decide on
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.
- 4d ago First seen · 80 lines · 228 tokens per session scan A 5a8719802be2
spec-consultant is an agent published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 3mo ago), licensed MIT. It adds 228 tokens to every session and 664 once invoked, about $0.0011 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 agents, from other repositories
section-writer
Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.
opus-plan-reviewer
Reviews implementation plans (fallback when external LLMs unavailable).
scaffolder
Creates repos and bootstraps projects for architecture components. Use after generating a blueprint with /architect:blueprint.
data-model-generator
Takes shared types and database definitions from a blueprint manifest and generates real ORM schemas (Prisma, SQLAlchemy, Mongoose, Drizzle) with migrations.
monitoring-setup
Generate observability stack config, metrics/tracing/logging code, dashboards, alerts, and SLO templates.
cicd-deployer
Takes the DevOps blueprint from an architecture and configures real CI/CD pipelines in GitHub Actions, Azure Pipelines, or GitLab CI. Sets up workflows, environment secrets, and deployment configs.