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/stainless-code/codemap/verify-after-each-stepnpx skills add stainless-code/codemap --skill verify-after-each-stepgit clone --depth 1 https://github.com/stainless-code/codemapWhat 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.00022 | $0.00824 |
| Opus 5 | $0.00011 | $0.00412 |
| Sonnet 5 | $0.00004 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
verify-after-each-step 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 2d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify after each step (full checklist)
Always-on priming: .agents/rules/verify-after-each-step.md.
Run matching checks on every file touched before moving to the next milestone. Pre-commit is the safety net, not the first line of defense.
Discover project scripts
- Read
package.jsonscriptsat the start of a task. - Read
lint-staged.config.js— which checks apply to which patterns (staged-only tsgo, paired co-located tests). - Never assume script names — verify they exist in
package.jsonbefore running.
Per-file check table (this repo)
From lint-staged.config.js — mirror these between milestones, not only at commit:
| File pattern | Checks |
|---|---|
*.{js,jsx,ts,tsx,mjs,mts,cjs,cts} |
bun run format:check, bun run lint |
*.{css,json,md,mdc,html,yaml,yml} |
bun run format:check |
*.{ts,tsx} |
bun run typecheck with a temporary tsconfig.lint-staged.json that includes only staged files under src/ (project-wide types still interconnect — use bun run typecheck if you need full-project certainty); bun test on co-located *.test.{ts,tsx} pairs when a staged src/ source file is present but its test file is not |
*.test.ts |
bun test (on changed test files) |
*.test.tsx |
bun test (on changed test files) |
scripts/**/*.test.mjs |
bun test (on changed test files) |
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.
- 2d ago First seen · 53 lines · 22 tokens per session scan A b3152a1911cd
verify-after-each-step is a skill published in the GitHub repository stainless-code/codemap (8 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 824 once invoked, about $0.0001 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
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
analyze-usage
Use when asked to analyze codescout tool usage, check for error patterns, audit tool health, generate a usage report, spot anti-patterns, or clear usage statistics to start fresh.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
mcp-headless-test
Run live tests of the Ariadne MCP server using Claude Code in headless mode. Tests tool discovery, invocation, and filtering. Use when validating MCP server changes or checking integration with Claude Code.
mcp-analytics
Check Ariadne MCP tool usage analytics — session counts, tool call stats, durations, and error rates.
release
Prepare a new release of Ariadne packages. Creates changesets, verifies build/tests, and drafts the PR to main.