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 instructions/krv-labs/topos/agents-mdgit clone --depth 1 https://github.com/Krv-Labs/toposWrote 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/instructions/krv-labs/topos/agents-md)<a href="https://agentmods.dev/instructions/krv-labs/topos/agents-md"><img src="https://agentmods.dev/badge/instructions/krv-labs/topos/agents-md.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.01012 | $0.01012 |
| Opus 5 | $0.00506 | $0.00506 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
topos AGENTS.md 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- topos CLAUDE.md — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenWiki
This repository has a generated openwiki/ evidence index. It is optional just-in-time context, not required startup reading.
- Treat source code and tests as authoritative. A brief's unknowns and review items are verification gaps, not automatic requirements.
- Prefer the narrowest quiet validation that proves the changed behavior. Preserve complete failure output.
The scheduled OpenWiki GitHub Actions workflow refreshes the repository wiki. Do not hand-edit generated OpenWiki pages unless explicitly asked; prefer updating source code/docs and letting OpenWiki regenerate.
Agent Skills
Canonical skill at skills/topos/SKILL.md — published to ClawHub and installable via Hermes taps.
Portable Agent Plugins 1.0 package: agent-plugin/ (plugin.json + skill + mcp.json).
| Runtime | Install |
|---|---|
| OpenClaw / ClawHub | openclaw skills install @Krv-Labs/topos |
| Hermes | hermes skills tap add Krv-Labs/topos then hermes skills install Krv-Labs/topos/topos |
| Agent Plugins client | Point the client at ./agent-plugin (requires topos on PATH) |
| Local (dev) | openclaw skills install ./skills/topos |
Validate with python scripts/check_skill.py and python scripts/check_agent_plugin.py (skill / plugin versions must match Cargo.toml; packaged skill must match skills/topos/SKILL.md).
ClawHub publish setup: add repo secret CLAWHUB_TOKEN — create a token at clawhub.ai (clh_...), then GitHub → Settings → Secrets and variables → Actions. The ClawHub Skill Publish workflow dry-runs on PRs and publishes on main (skills/**) and v* tags. Manual fallback: clawhub skill publish ./skills/topos --owner Krv-Labs.
OpenWiki CI (repo-owned policy)
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.
- today Changed · +3 lines · +83 tokens per session 342f41d02200
- 4d ago First seen · 69 lines · 929 tokens per session scan A 21fefc2da73a
topos AGENTS.md is an instructions file published in the GitHub repository Krv-Labs/topos (25 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 1,012 tokens to every session, about $0.0051 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.