no-mistakes is a local Git proxy that validates changes in an isolated worktree before forwarding a push to the real remote and opening a pull request. It is for developers and coding agents that want automated checks, safe fixes, CI repair, and human review before changes are published.
Borrowing it
Nothing to install: this file belongs to kunchenguid/no-mistakes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kunchenguid/no-mistakes/main/.agents/skills/documentation-guidance/SKILL.mdgit clone --depth 1 https://github.com/kunchenguid/no-mistakesWrote 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/kunchenguid/no-mistakes/documentation-guidance)<a href="https://agentmods.dev/skills/kunchenguid/no-mistakes/documentation-guidance"><img src="https://agentmods.dev/badge/skills/kunchenguid/no-mistakes/documentation-guidance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kunchenguid/no-mistakes/documentation-guidance"><img src="https://agentmods.dev/badge/skills/kunchenguid/no-mistakes/documentation-guidance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 18 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.1 | $0.00036 | $0.00853 |
| Opus 5.5 | $0.00014 | $0.00341 |
| Sonnet 5.5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
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 29d 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.
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.
Combined Document+Lint Housekeeping Pass
- When
commands.lintis empty, the document step performs both duties in one agent invocation and stashes the lint half onRunShared(consume-once); the lint step consumes it instead of paying a second cold pass. Neither duty is ever silently dropped: a skipped pass, untrusted structured output, or a lint fix round falls back to lint's own agent pass. Configuredcommands.lintstays a first-class deterministic gate. Uncategorized findings fail safe to the stricter documentation gate. - The document prompt enforces the placement policy (one owner per fact, stale duplicates become pointers, no AGENTS.md postmortems, scope limited to docs the change made stale). Do not reintroduce exhaustive-corpus-sweep language; it caused doc commits in 90 of 121 audited PRs. Contract test:
TestDocumentStep_PromptAppliesPlacementPolicy; behavior tests:internal/pipeline/steps/housekeeping_test.go. agent.MemoryFilesRule(internal/agent/memory_files.go) limits independently initiated memory-file edits without excluding memory-file changes from review or prompted fixes. It is appended to the review/test/lint/PR/intent prompts and throughfixerPromptto shared fix turns and CI repair; rebase/merge conflict resolvers useagent.MemoryFilesConflictRule, and the document prompt has its own correction-only rule. Seedocs/src/content/docs/reference/pipeline-steps.mdfor the user-facing contract. Prompt-contract tests:internal/pipeline/steps/memory_files_test.go,internal/intent/*_test.go.
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.
- 29d ago Changed · +6 lines · +15 tokens per session f54440e890b0
- 1mo ago First seen · 22 lines · 21 tokens per session scan A e05024485d35
documentation-guidance is a skill published in the GitHub repository kunchenguid/no-mistakes (8,945 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 853 once invoked, about $0.0001 per session on Opus 5.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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.