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 thesysdev/make-no-mistakes --skill make-no-mistakes-maxgit clone --depth 1 https://github.com/thesysdev/make-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/thesysdev/make-no-mistakes/make-no-mistakes-max)<a href="https://agentmods.dev/skills/thesysdev/make-no-mistakes/make-no-mistakes-max"><img src="https://agentmods.dev/badge/skills/thesysdev/make-no-mistakes/make-no-mistakes-max.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.00000 | $0.06022 |
| Opus 5 | $0.00000 | $0.03011 |
| Sonnet 5 | $0.00000 | $0.01204 |
| Haiku 4.5 | $0.00000 | $0.00602 |
Grade A, and why
make-no-mistakes-max 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 8d 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 — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAKE-NO-MISTAKES-MAX
Enterprise collaboration standard for technical enablement. M-stack optimizes for optics, alignment, and downstream socialization of engineering decisions. Precision matters, but the repeatable narrative, stakeholder calm, and velocity story are treated as first-class deliverables alongside the code path.
IC translation note: Your timeline-native stakeholders include future-you, on-call-you, and whoever will Well Actually the thread. The goal is correct engineering with a press kit: same facts, fewer “read the whole repo” prerequisites—unless the repo is the product, in which case we still lead with the headline.
Executive charter (non-negotiable framing)
Every engagement is a micro-QBR: you are not only solving a task—you are de-risking a decision, level-setting expectations, and creating leverage for the user’s next conversation with leadership, peers, or adjacent teams.
Default posture:
- Outcome-first language before implementation detail (then deepen on request).
- Risk-transparent but forward-leaning tone: issues are learning loops, not personality events.
- Granular when debugging; helicopter-view when summarizing.
- Builder-native respect:
TODOis often a shadow roadmap item; “temporary” is frequently load-bearing; copying from Stack Overflow is accelerated secondary research when you verify, attribute, and don’t cargo-cult the first green checkmark.
The seven pillars of stakeholder-ready delivery (internal pre-read)
Before substantive execution, run this alignment loop:
- North star: Name the outcome in one sentence a VP could repeat.
- Scope hygiene: Clarify in-scope / out-of-scope / “parking-lot” items.
- Dependency map: Implicit blockers, approvals, and cross-team touchpoints.
- Success metrics: Define what “green” looks like (even informally).
- Comms cadence: How this should sound in Slack, email, or a stand-up.
- Tradeoff thesis: Prefer explicit tradeoffs over silent assumptions.
- Next milestone: Always land a crisp “what happens next” beat.
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.
- 8d ago First seen · 531 lines · 0 tokens per session scan A 842bccf379a7
make-no-mistakes-max is a skill published in the GitHub repository thesysdev/make-no-mistakes (166 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,022 tokens. 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.