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 RaNDoM6913/claude-code-superkit --skill output-enforcementgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/output-enforcement)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/output-enforcement"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/output-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/random6913/claude-code-superkit/output-enforcement"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/output-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.00040 | $0.00771 |
| Opus 5.5 | $0.00016 | $0.00308 |
| Sonnet 5.5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
output-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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope-Bound Completeness
Complete the authorized deliverable and report its actual state. Completeness is judged against the requested result and applicable acceptance criteria, not the number of files printed or the presence of particular comment strings.
Before Writing
- Identify the requested outcome, allowed scope, delivery form, and required verification. Reuse an accepted plan; resolve only ambiguities that materially affect the result.
- Inspect the affected code and local contracts before changing them. Identify required callers, imports, types, configuration, and tests within the change's dependency path. Preserve unrelated files, behavior, and existing user edits.
- Choose a suitable artifact. A scoped patch may be complete in its existing project context. A requested standalone program must include its required pieces and setup. A read-only review, explanation, or plan may be prose and does not authorize implementation.
Implement the Required Change
- Supply all logic needed for the authorized result, including its required error paths and integration. Do not replace required behavior with empty bodies, canned success, dummy data, or comments promising later implementation.
- Use focused edits and preserve surrounding code. A patch need not reproduce unchanged file contents. A full replacement file must retain all required content; omission markers must not stand in for code that the replacement needs.
- Assess TODOs, comments, ellipses, stubs, and fixtures by their role. Legitimate syntax, explanatory comments, existing deferred work, and explicitly requested scaffolds or examples are allowed. Label illustrative or intentionally partial output clearly; do not pass it off as the requested working implementation.
- Do not fix unrelated TODOs or expand the task merely to make a file appear finished. If a newly discovered dependency exceeds authorization, report the concrete gap and its effect on completion.
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.
- yesterday Changed · +2 lines · -4 tokens per session f69e5a6305bb
- 1mo ago First seen · 70 lines · 44 tokens per session scan A 203bac4fc164
output-enforcement is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 771 once invoked, about $0.0002 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-31.
Other skills, from other repositories
nav-loop
Run tasks until complete with structured completion signals. Auto-invoke when user says "run until done", "keep going until complete", "iterate until finished", "loop mode", "autonomous mode".
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
nav-diagnose
Detect quality drops in AI output and prompt re-anchoring. Auto-triggers after repeated corrections, context confusion, or when user says "something seems off", "you're not getting this".
git-commit
A guided Git commit workflow that examines changes and creates a commit message using the Conventional Commits format, a shared style for labeling changes such as features, fixes, tests, or documentation.
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
impeccable
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for…