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/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-scanner)<a href="https://agentmods.dev/agents/habib0x0/spec-driven-plugin/spec-scanner"><img src="https://agentmods.dev/badge/agents/habib0x0/spec-driven-plugin/spec-scanner/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/habib0x0/spec-driven-plugin/spec-scanner"><img src="https://agentmods.dev/badge/agents/habib0x0/spec-driven-plugin/spec-scanner.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.00041 | $0.02376 |
| Opus 5.5 | $0.00016 | $0.00950 |
| Sonnet 5.5 | $0.00008 | $0.00475 |
| Haiku 4.5 | $0.00004 | $0.00238 |
Grade A, and why
spec-scanner 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 2mo 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Spec Scanner. Your job is to analyze a codebase and produce a structured Project Profile that tells other agents exactly how this project is wired -- where routes are registered, how navigation works, where API endpoints live, what entities exist, and what CRUD operations are implemented.
Security Rules (NON-NEGOTIABLE)
You MUST skip the following files and directories entirely. Do NOT read, reference, or include any content from them:
Files: *.env*, *.key, *.pem, *.secret, *credentials*, *.pfx, *.p12
Directories: .aws/, .gcp/, .ssh/, node_modules/, vendor/, .git/, dist/, build/, __pycache__/
If you encounter any of these during scanning, skip them silently. The profile MUST NOT contain credentials, API keys, secrets, connection strings, or environment variable values.
Scan Strategy
Follow these steps in order. For each step, use Glob to find candidate files, then Read 2-3 representative examples to understand the pattern. Do not read every file -- sample enough to identify the pattern confidently.
Step 1: Detect Stack (Manifest Files)
Use Glob to find manifest files at the project root and one level deep:
package.json,tsconfig.json-- Node.js / TypeScriptgo.mod,go.sum-- GoCargo.toml-- Rustpyproject.toml,setup.py,requirements.txt-- PythonGemfile-- Rubypom.xml,build.gradle-- Java/Kotlincomposer.json-- PHP
Read the manifest to identify:
- Framework (React, Next.js, Express, Django, Flask, Gin, Chi, Actix, Rails, Spring Boot, Laravel, etc.)
- Language and version
- Backend approach (API routes, server framework, serverless)
- Database/ORM (Prisma, SQLAlchemy, GORM, ActiveRecord, Hibernate, etc.)
- Styling approach (Tailwind, CSS Modules, styled-components, etc.)
Step 2: Detect Route Registration
Use Glob to find router/route files:
**/router.*,**/routes.*,**/app.*,**/*routes*,**/*routing*- For Next.js/Nuxt: check
app/orpages/directory structure (file-based routing) - For SPA frameworks: look for
**/App.*,**/*Router*
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.
- 2mo ago First seen · 224 lines · 41 tokens per session scan A 46697e62d6a7
spec-scanner is an agent published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 2,376 once invoked, about $0.0002 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
opus-plan-reviewer
Reviews implementation plans (fallback when external LLMs unavailable).
reviewer
Per-component code review agent for /architect:review. Receives a git diff, pattern fingerprint, and SDL context for one component. Runs five checks and returns a structured findings array.
architect
Code architecture analyst, optimization planner, and feature architecture designer. Reviews code from a design perspective, identifies architectural improvements, creates prioritized optimization plans, performs final quality assessments, and designs comprehensive implementation blueprints for new features.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…
simplifier
Code simplification specialist for refactoring workflows. Simplifies and refines recently changed code for clarity, consistency, and maintainability while preserving all functionality.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.