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/kunchenguid/no-mistakes/documentation-guidancenpx skills add kunchenguid/no-mistakes --skill documentation-guidancegit clone --depth 1 https://github.com/kunchenguid/no-mistakesWhat 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.00021 | $0.00501 |
| Opus 5 | $0.00010 | $0.00251 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
documentation-guidance 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 yesterday.
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.
What it actually says
Documentation
- Keep
README.mdconcise and high-level; the bar needs to be extremely high for what shows up there. - Most documentation lives in
docs/, the published docs site. - One owner per fact:
docs/src/content/docs/reference/global-config.mdanddocs/src/content/docs/reference/repo-config.mdown configuration keys,docs/src/content/docs/reference/environment.mdowns environment variables and the telemetry local/remote split,docs/src/content/docs/concepts/daemon.mdowns the daemon lifecycle model, and guides pages explain purpose and link to those owners instead of restating tables and examples. - The
document.instructionsblock in.no-mistakes.yamlstates this ownership map for the pipeline's document step; update it when ownership moves.
Agent-Guidance Surfaces
skills/no-mistakes/SKILL.mdis generated: the source of truth is thebodyconstant ininternal/skill/skill.go. Edit the body, thenmake skill;make lintfails CI on drift. Never editSKILL.mddirectly.no-mistakes initships this rendering to agents at user level.- Agent-driving guidance is owned by the skill body and the live
axioutput strings (internal/cli/axi*.go);docs/src/content/docs/guides/agents.mdcarries only the canonical invariant sentences pinned byinternal/cli/axi_guidance_test.goplus a pointer to the skill. When you change driving guidance, change the skill body and the point-of-useaxistrings together; that drift test is the sync check. - The shared default test-quality rule lives in
internal/testguidance; render it only into the task-first skill and pipeline roles that can author, repair, or review tests. Its fake-agent prompt tests are the intentional generated-interface contract, not source-text checks. - Review auto-fix is disabled by default (
auto_fix.review: 0inconfig.goautoFixDefaults), so blocking and ask-user review findings park for an agent decision; keep the skill, the liveaxigatenote, and docs qualified if you touch review auto-fix.
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.
- yesterday First seen · 22 lines · 21 tokens per session scan A e05024485d35
documentation-guidance is a skill published in the GitHub repository kunchenguid/no-mistakes (7,965 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 501 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…