Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/commands/dinhnguyenngoc/spec-driven-claude-code/discover-system)<a href="https://agentmods.dev/commands/dinhnguyenngoc/spec-driven-claude-code/discover-system"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/discover-system.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.00030 | $0.03577 |
| Opus 5 | $0.00015 | $0.01788 |
| Sonnet 5 | $0.00006 | $0.00715 |
| Haiku 4.5 | $0.00003 | $0.00358 |
Grade A, and why
discover-system 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/discover-system — System-Level Map (Multi-Repo)
"Understand the whole product before changing one service."
Purpose
For a microservices product spread across many repos, build a system-wide map by aggregating the per-repo discovery artifacts. This is the system-scope counterpart of /discover (which is repo-scope). Read-only · run once + incremental.
Workspace Mode: this is the ONE command that runs AT the workspace root itself — do not scope it to a member repo.
One-way by design.
/discover-systemreads per-repo output → producesarchitecture/system/as documentation to understand the system. Individual services keep developing + testing independently; they do NOT take a runtime dependency on the system layer. Cross-service safety = backward-compat discipline (rules/brownfield.md). Full convention:../references/microservices-multirepo.md.
When to Use
- Onboarding an existing multi-repo microservices product (one-time), or refreshing the map after services were added/changed.
- NOT for a single-repo project — use
/discover.
Prerequisites
- A workspace: all service repos checked out under one parent folder (clone them side by side if they live in separate repos — Pattern B in the reference).
- Per-repo Phase A done for each service — every repo has:
docs/CODEBASE_MAP.md(from/discover)specs/SPEC.mdwith@USids (from reverse-/spec)architecture/ARCHITECTURE.md+architecture/api/openapi.yaml+ §Service Contracts (from reverse-/arch— seearch.md§3.2)- a
Service iddeclared in itsProject Profile.
A repo missing any of the above → list it in the catalog as
⚠️ incomplete; do NOT fabricate its boundary/contracts.
Boundary — READ-ONLY
/discover-system reads per-repo artifacts and writes only architecture/system/. It does NOT modify any service repo's source, spec, or architecture. It reads compact artifacts (CODEBASE_MAP rows, §Service Contracts tables, openapi, SPEC @US), NOT full service code.
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 · 159 lines · 30 tokens per session scan A a024876eeadd
discover-system is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 3,577 once invoked, about $0.0002 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-30.
Other commands, from other repositories
spec-kitty.implement
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
generate-design-md
Génère un DESIGN.md à la racine du projet à partir du template Claude Craft + analyse des sources UI existantes (Tailwind, tokens, CSS).
generate-hook
Génération Custom Hook React.
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
wayfind
Plan a chunk of work too big for one agent session as a shared decision map: map.md + typed decision tickets in the mega-goal folder, resolved one per session through the kit's own grill/prototype/research machinery, until nothing is left to decide. Then hand off to /kit:spec or a ROADMAP, never straight to execute.