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 commands/keithwhatling/topo/topo-validategit clone --depth 1 https://github.com/KeithWhatling/ToPOWrote 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/keithwhatling/topo/topo-validate)<a href="https://agentmods.dev/commands/keithwhatling/topo/topo-validate"><img src="https://agentmods.dev/badge/commands/keithwhatling/topo/topo-validate.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.00046 | $0.01233 |
| Opus 5 | $0.00023 | $0.00616 |
| Sonnet 5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
topo-validate 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/topo-validate
Run a full consistency check on docs/solution-map.topo and regenerate the dependency graph.
Step 1: Load the Map
Read docs/solution-map.topo. If it does not exist, tell the user to run /init-project
or create it from the template.
Step 2: Parse All Component Blocks
Extract every TOPO block and build an in-memory index:
- Component ID (tag + name, e.g.
[SL] ValidateItem) - All
depends_ontable entries - All
depended_on_bytable entries - For
[CL]blocks: theparityvalue - For
[DE]blocks: theserver-logic,client-logic,ui-controlslists - For all blocks: the
lifecyclevalue
Step 3: Bidirectional Dependency Check
For every depends_on entry pointing to target [X] Name:
- Verify
[X] Nameexists in the map - Verify
[X] Namehas adepended_on_byentry referencing this component
For every depended_on_by entry pointing to source [X] Name:
- Verify
[X] Nameexists in the map - Verify
[X] Namehas adepends_onentry referencing this component
Report: DEPENDENCY MISMATCH: [SL] ValidateItem depends_on [DE] contoso_itemtype, but [DE] contoso_itemtype does not list [SL] ValidateItem in depended_on_by
Step 4: Orphan Reference Check
Any component referenced in depends_on, depended_on_by, server-logic lists,
client-logic lists, ui-controls lists, parity references, or backing-logic
references that has no block in the map.
Report: ORPHAN REFERENCE: [SF] InventoryApiClient referenced by [SL] ValidateItem but has no [SF] block
Step 5: Entity Cross-Reference Check
For every [DE] block:
- Every component listed in
server-logicmust have a corresponding[SL]block - Every component listed in
client-logicmust have a corresponding[CL]block - Every component listed in
ui-controlsmust have a corresponding[UC]block
Report: MISSING BLOCK: [SL] ValidateItem listed in [DE] contoso_listlineitem server-logic but no [SL] block exists
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 · 122 lines · 46 tokens per session scan A 57b91ee8141f
topo-validate is a command published in the GitHub repository KeithWhatling/ToPO (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,233 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.