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 skills add stevesolun/ctx --skill no-mistakesgit clone --depth 1 https://github.com/stevesolun/ctxWrote 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/stevesolun/ctx/no-mistakes)<a href="https://agentmods.dev/skills/stevesolun/ctx/no-mistakes"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/no-mistakes.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.1 | $0.00067 | $0.00442 |
| Opus 5 | $0.00034 | $0.00221 |
| Sonnet 5 | $0.00013 | $0.00088 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
no-mistakes 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 7d 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
no-mistakes
no-mistakes is a local git gate. It validates committed branch changes before
they reach upstream and reports decision points in machine-readable TOON.
Preconditions
- Work is committed.
- Current branch is a feature branch, not the default branch.
- The repository has been initialized with
no-mistakes init. - The intent is explicit: what the user wanted to accomplish, not only a diff summary.
Run
no-mistakes axi run --intent "<what the user set out to accomplish>"
Use the user's exact objective as the intent, enriched with material decisions and constraints learned during the work.
Decision Loop
If output contains a gate: object, inspect each finding:
auto-fix: make the mechanical fix, then respond withfix.no-op: approve or continue when nothing needs changing.ask-user: stop and relay the finding to the user before responding.
Useful commands:
no-mistakes axi respond --action approve
no-mistakes axi respond --action fix --findings <id1,id2> --instructions "<guidance>"
no-mistakes axi respond --action skip
no-mistakes axi status
no-mistakes axi logs --step <name> --full
no-mistakes axi abort
Output Contract
checks-passed: CI is green and the PR is ready for human review/merge.passed: the gate completed.failedorcancelled: inspect output and fix the reported issue.
Do not silently approve ask-user findings unless the user explicitly gave
standing consent such as --yes.
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.
- 7d ago First seen · 60 lines · 67 tokens per session scan A 66189e18fcab
no-mistakes is a skill published in the GitHub repository stevesolun/ctx (583 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 442 once invoked, about $0.0003 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
release
Versioning and CHANGELOG: SemVer mapped from Conventional Commits, Keep a Changelog format, tagging, pre-release gates. Use when cutting a version: bumping, writing the CHANGELOG entry, or tagging.
seal
Ships a feature — simplify pass, certify, commit, PR, CI monitoring, review loop, merge. Use when a feature branch is verified and ready to ship.
trace-scan
Trace scan (§4.1/§4.2): before a commit, scans the staged changes and the message for AI traces (co-author trailers, footers, robot emoji, tool names) and vendor template names. The git hooks apply it automatically.
github
GitHub-centric templates — pull requests, issue triage, repo automation.
int-github-review
Review GitHub repos — open PRs, community issues, stars/forks, releases, contributors. Use when user says 'check github', 'github review', 'repo status', 'open PRs', 'github issues', 'repository status', or any reference to checking GitHub repos status.
gamedev-team-release
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.