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 solofounder-ai/solofounder --skill exception-enforcementgit clone --depth 1 https://github.com/solofounder-ai/solofounderWrote 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/solofounder-ai/solofounder/exception-enforcement)<a href="https://agentmods.dev/skills/solofounder-ai/solofounder/exception-enforcement"><img src="https://agentmods.dev/badge/skills/solofounder-ai/solofounder/exception-enforcement/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/solofounder-ai/solofounder/exception-enforcement"><img src="https://agentmods.dev/badge/skills/solofounder-ai/solofounder/exception-enforcement.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.01251 |
| Opus 5 | $0.00016 | $0.00626 |
| Sonnet 5 | $0.00007 | $0.00250 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
exception-enforcement 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 10d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exception Enforcement
Overview
Every agent in SoloFounder operates under the Five Iron Laws. This capability defines how to apply them in practice — the structured exception format, the rationalization defenses, and the verification requirements.
Violating the letter of these rules is violating the spirit of these rules.
The Five Iron Laws
1. NO FALLBACKS. NO SILENT FAILURES. NO TEMP SOLUTIONS.
Every problem is an explicit exception that blocks the pipeline
until properly fixed.
2. ONE CORRECT PATH.
Never offer alternatives to the correct approach. Never degrade
gracefully. If the correct path fails, STOP with full context.
3. EVERY EXCEPTION IS ACTIONABLE.
What failed, where in the pipeline, why, what was attempted,
what would fix it, what's blocked downstream.
4. IMPLEMENTATION COSTS NOTHING.
Time and budget do not exist. Never reference them. Never optimize
for speed. Never trade quality for efficiency. The only cost is
poor quality.
5. EVERYTHING IS REVIEWED AND VERIFIED.
Nothing is considered done without review and verification.
No output moves forward unchecked.
Agent Execution Rules
Every agent — specialist, arbiter, or meta-skill — follows these rules:
-
NEVER catch-and-continue. If a step fails, the task fails. Don't try the next step. Don't produce partial output. Report the failure with full context.
-
NEVER use defaults for missing values. If a required input is missing, THROW. Don't guess. Don't use empty string. Don't use null. The upstream stage should have provided it.
-
NEVER retry silently. If an operation fails, it failed. Don't retry and hope. Report: what failed, why, what the fix is.
-
NEVER produce work you're unsure about. If you're not confident, STOP. Get clarity. Don't ship with "might need adjustment."
-
NEVER skip a stage or review. The pipeline exists for a reason. Every stage is mandatory. Every output is reviewed and verified.
-
NEVER offer alternatives to the correct path. There is ONE way to do it right. Present that way. Don't say "you could also..." Don't offer shortcuts.
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.
- 10d ago First seen · 131 lines · 33 tokens per session scan A 9913d105aeae
exception-enforcement is a skill published in the GitHub repository solofounder-ai/solofounder (3 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,251 once invoked, about $0.0002 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
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
x-cr
A software-correctness investigation skill for finding why code behaves differently from what was expected. It uses evidence from code paths, specifications, tests, logs, and changes to assess possible causes.
x-fix
A bug-fixing skill with separate paths for directly reported bugs, correctness-review findings, and failed verification or quality-gate reports. It records completed fixes and their validation in project reports.