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.
git 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/commands/povvo/claudikins-kernel/verify)<a href="https://agentmods.dev/commands/povvo/claudikins-kernel/verify"><img src="https://agentmods.dev/badge/commands/povvo/claudikins-kernel/verify/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/commands/povvo/claudikins-kernel/verify"><img src="https://agentmods.dev/badge/commands/povvo/claudikins-kernel/verify.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.00027 | $0.03126 |
| Opus 5.5 | $0.00011 | $0.01250 |
| Sonnet 5.5 | $0.00005 | $0.00625 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
claudikins-kernel:verify 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 2mo 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. Try primary method (screenshot/curl/run) How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claudikins-kernel:verify Command
You are orchestrating a verification workflow that ensures code actually works before shipping.
Flags
| Flag | Effect |
|---|---|
--branch NAME |
Verify specific branch (default: current) |
--scope SCOPE |
test|lint|types|all (default: all) |
--skip-simplify |
Skip cynic polish pass |
--fix-lint |
Auto-apply lint fixes |
--fast-mode |
60-second iteration cycles |
--session-id ID |
Resume previous session by ID |
--timing |
Show phase durations for velocity tracking |
--list-sessions |
Show available sessions for resume |
--resume |
Resume from last checkpoint |
--status |
Show current verification status |
Merge Strategy
JQ merge - verification outputs are combined with jq -s 'add'.
Philosophy
"Evidence before assertions. Always." - Verification philosophy
- Verification is the gate between claudikins-kernel:execute and claudikins-kernel:ship
- Claude MUST see its code working (not just tests passing)
- Human checkpoint with comprehensive report
- Exit code 2 blocks claudikins-kernel:ship until verification passes
- All Opus models for agents (no compromises on judgement)
State Management
State file: .claude/verify-state.json
{
"session_id": "verify-YYYY-MM-DD-HHMM",
"execute_session_id": "exec-YYYY-MM-DD-HHMM",
"branch": "execute/task-1-feature",
"started_at": "ISO timestamp",
"status": "initialising|verifying|completed|failed",
"phases": {
"test_suite": { "status": "pending|PASS|FAIL" },
"lint": { "status": "pending|PASS|FAIL" },
"type_check": { "status": "pending|PASS|FAIL" },
"output_verification": { "status": "pending|PASS|FAIL" },
"code_simplification": { "status": "pending|PASS|FAIL|skipped" }
},
"all_checks_passed": false,
"human_checkpoint": {
"prompted_at": null,
"decision": null,
"caveats": []
},
"unlock_ship": false
}
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.
- 2mo ago First seen · 550 lines · 27 tokens per session scan A 4fd393a84205
claudikins-kernel:verify is a command published in the GitHub repository povvo/claudikins-kernel (127 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 3,126 once invoked, about $0.0001 per session on Opus 5.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.
claudikins-kernel:verify compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| claudikins-kernel:verifypovvo/claudikins-kernel | Command | 127 | 6mo ago | MIT | A | 27 | Claude Code |
| evaluategrainulation/grainulator | Command | 86 | yesterday | MIT | A | 0 | Claude Code |
| prototypegrainulation/grainulator | Command | 86 | yesterday | MIT | A | 0 | Claude Code |
| postspencermarx/open-code-review | Command | 382 | 5d ago | Apache-2.0 | A | 11 | Claude Code |
| showspencermarx/open-code-review | Command | 382 | 5d ago | Apache-2.0 | A | 7 | Claude Code |
| historyspencermarx/open-code-review | Command | 382 | 5d ago | Apache-2.0 | A | 6 | Claude Code |
| nextgrainulation/grainulator | Command | 86 | yesterday | MIT | A | 0 | Claude Code |