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 povvo/claudikins-kernel --skill strict-enforcementgit clone --depth 1 https://github.com/povvo/claudikins-kernelWrote 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/povvo/claudikins-kernel/strict-enforcement)<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/strict-enforcement"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/strict-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/povvo/claudikins-kernel/strict-enforcement"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/strict-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.00044 | $0.02610 |
| Opus 5 | $0.00022 | $0.01305 |
| Sonnet 5 | $0.00009 | $0.00522 |
| Haiku 4.5 | $0.00004 | $0.00261 |
Grade A, and why
strict-enforcement scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **See it working** - Screenshots, curl responses, CLI output. Actual evidence. How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strict Enforcement Verification Methodology
When to use this skill
Use this skill when you need to:
- Run the
claudikins-kernel:verifycommand - Validate implementation before shipping
- Decide pass/fail verdicts
- Check code integrity after changes
- Enforce cross-command gates
Core Philosophy
"Evidence before assertions. Always." - Verification philosophy
Never claim code works without seeing it work. Tests passing is not enough. Claude must SEE the output.
The Three Laws
- See it working - Screenshots, curl responses, CLI output. Actual evidence.
- Human checkpoint - No auto-shipping. Human reviews evidence and decides.
- Exit code 2 gates - Verification failures block claudikins-kernel:ship. No exceptions.
Verification Phases
Phase 1: Automated Quality Checks
Run the automated checks first. Fast feedback.
| Check | Command Pattern | What It Catches |
|---|---|---|
| Tests | npm test / pytest / cargo test |
Logic errors, regressions |
| Lint | npm run lint / ruff / clippy |
Style issues, common bugs |
| Types | tsc / mypy / cargo check |
Type mismatches, interface drift |
| Build | npm run build / cargo build |
Compilation errors, bundling issues |
Flaky Test Detection (C-12):
Test fails?
├── Re-run failed tests
├── Pass 2nd time?
│ └── Yes → STOP: [Accept flakiness] [Fix tests] [Abort]
└── Fail 2nd time?
├── Run isolated
└── Still fail? → STOP: [Fix] [Skip] [Abort]
Phase 2: Output Verification (catastrophiser)
This is the feedback loop that makes Claude's code actually work.
| Project Type | Verification Method | Evidence |
|---|---|---|
| Web app | Start server, screenshot, test flows | Screenshots, console logs |
| API | Curl endpoints, check responses | Status codes, response bodies |
| CLI | Run commands, capture output | stdout, stderr, exit codes |
| Library | Run examples, check results | Output values, test coverage |
| Service | Check logs, verify health endpoint | Log patterns, health responses |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/advanced-verification.md 9.5 KB
- references/agent-integration.md 11 KB
- references/cynic-rollback.md 7.1 KB
- references/lint-fix-validation.md 6.2 KB
- references/red-flags.md 8.5 KB
- references/test-timeout-handling.md 6.2 KB
- references/type-check-confidence.md 6.6 KB
- references/verification-checklist.md 11 KB
- references/verification-method-fallback.md 7.1 KB
- references/verify-state-compression.md 7.1 KB
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 · 297 lines · 44 tokens per session scan A 3614c9f03428
strict-enforcement is a skill published in the GitHub repository povvo/claudikins-kernel (126 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 2,610 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
laravel-testing
Use when testing controllers, services, or models, or implementing TDD on Laravel 13 with Pest 4 / PHPUnit 12.
react-testing
Testing Library for React 19 - render, screen, userEvent, waitFor, Suspense. Use when writing tests for React components with Vitest.
verification
Use when marking a task complete, finishing a feature, or claiming a bug fixed -- verifies functional resolution before closing. Do NOT use for lint/quality checks (use sniper AFTER this).
go-concurrency
Use when writing or reviewing Go concurrency — goroutines, channels, errgroup, context cancellation, or goroutine leaks. Not for sequential idioms (go-core-idioms).
php-testing
Use when writing/configuring tests on a non-Laravel PHP project — PHPUnit vs Pest. Do NOT use for Laravel test helpers or quality tooling (php-quality-tooling).
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).