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 niels-emmer/myace --skill exception-documentationgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/exception-documentation)<a href="https://agentmods.dev/skills/niels-emmer/myace/exception-documentation"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/exception-documentation/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/niels-emmer/myace/exception-documentation"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/exception-documentation.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.00035 | $0.00789 |
| Opus 5 | $0.00017 | $0.00394 |
| Sonnet 5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
Exception Documentation 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 5d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Some invariants genuinely can't be met in every situation — a legacy client needs a public endpoint, a third-party system has no workload-identity support and needs a static key. That's fine, occasionally, as long as it's a decision someone made on purpose and can find again later. This skill is the template that turns "we had to break the rule here" into a durable, reviewable record instead of a comment nobody will trust six months from now.
When to use it
Any time a change violates one of the standing invariants (private-by-default networking, managed identity over secrets, naming/tagging convention, remote state with locking) and there's a genuine reason it has to. Write the exception before or alongside implementing the deviation — not after the fact when someone asks about it.
Required fields
Every documented exception needs all four of these — a deviation missing any one of them is not a documented exception, it's an undocumented one with extra steps:
- Rationale — Why can't this resource follow the rule? Be specific about the actual constraint (e.g. "third-party partner's system only supports static API keys, no OAuth/federation option" or "legacy consumer application requires a public endpoint until its Q3 migration lands"), not a restatement of the exception itself.
- Compensating control — What's in place instead to keep the risk bounded? For a public endpoint: IP allow-listing, WAF rules, rate limiting. For a static secret: short rotation interval, storage in a secret manager rather than in code, scoped-down permissions. A compensating control that's just "we'll be careful" is not a compensating control.
- Approver — A named individual (not a team, not "leadership") who reviewed this specific exception and signed off on it. If no one can be named, the exception isn't approved yet.
- Expiry / review date — A concrete date this exception gets revisited, not "permanent" or "TBD." If the underlying constraint is genuinely permanent, that's still worth re-confirming on a cadence (e.g. annually) rather than assumed forever.
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.
- 5d ago First seen · 46 lines · 35 tokens per session scan A ad9ac02c95fa
Exception Documentation is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 789 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-09-03.
Other skills, from other repositories
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
implementing-gdpr-data-protection-controls
The General Data Protection Regulation (EU) 2016/679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill cover.
implementing-pci-dss-compliance-controls
PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements.
Agent Compliance & Security Assessment
Comprehensive compliance and security self-assessment for AI agents. 14-check framework producing a structured threat model + compliance report with RED/AMBER/GREEN ratings across security, governance, EU AI Act readiness, oversight quality, and NIST alignment domains. Includes automation bias detection, audit trail…
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
fee-billing
Build and manage advisory fee billing operations from fee schedule design through calculation, collection, revenue recognition, and compliance disclosure. Use when the user asks about tiered or breakpoint fee schedules, billing cycle configuration, AUM valuation for billing, direct-debit vs invoice collection, GAAP…