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 skills/keithwhatling/topo/guidesnpx skills add KeithWhatling/ToPO --skill guidesgit 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/skills/keithwhatling/topo/guides)<a href="https://agentmods.dev/skills/keithwhatling/topo/guides"><img src="https://agentmods.dev/badge/skills/keithwhatling/topo/guides.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.00135 | $0.01253 |
| Opus 5 | $0.00068 | $0.00626 |
| Sonnet 5 | $0.00027 | $0.00251 |
| Haiku 4.5 | $0.00014 | $0.00125 |
Grade A, and why
topo 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TOPO Skill — Topology of Platform Objects
Purpose
The TOPO map (docs/solution-map.topo) is the single source of truth for how
components relate to each other and why they exist. This skill defines how to
read, write, and maintain .topo files.
Full language reference: docs/topo-language-spec.md
SOPs: docs/topo-standard-operating-procedures.md
File extension: .topo (markdown-compatible; associate with markdown syntax highlighting)
1. Quick Reference — Component Tags
| Tag | Type | When to create a block |
|---|---|---|
[DE] |
Data Entity | New table/collection/document designed |
[DF] |
Data Field | Field added that drives logic |
[DR] |
Data Relationship | Relationship between entities |
[SL] |
Server Logic | Server-side component created |
[CL] |
Client Logic | Client-side component created |
[API] |
API | Exposed interface created |
[SF] |
Shared Function | Reusable function created |
[BP] |
Background Process | Async/scheduled process created |
[UC] |
UI Control | Custom UI component created |
[CFG] |
Config Pattern | Config entity + handler pair created |
[IB] |
Integration Boundary | External system connection created |
2. Quick Reference — Relationship Types
| Type | Meaning | Impact |
|---|---|---|
depends_on |
A requires B | B's failure breaks A |
serves |
A provides to B | A's change may break B |
triggers |
A causes B to run | A's changes affect B |
flows_to |
Data moves A to B | A's schema may break B |
realizes |
A implements B | B's contract change requires A update |
configures |
A provides config to B | A's schema affects B |
contains |
B is part of A | B's change always impacts A |
subscribes_to |
A listens to B | B's event schema affects A |
maps_to |
Abstract to concrete | Platform profile mapping |
supersedes |
A replaces B | B's dependents should migrate |
3. Bidirectional Dependency Rule
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 113 lines · 135 tokens per session scan A 896249275140
topo is a skill published in the GitHub repository KeithWhatling/ToPO (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 135 tokens to every session and 1,253 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…