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/Pinperepette/context-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/agents/pinperepette/context-kernel/kernel-verifier)<a href="https://agentmods.dev/agents/pinperepette/context-kernel/kernel-verifier"><img src="https://agentmods.dev/badge/agents/pinperepette/context-kernel/kernel-verifier/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/agents/pinperepette/context-kernel/kernel-verifier"><img src="https://agentmods.dev/badge/agents/pinperepette/context-kernel/kernel-verifier.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.00076 | $0.00688 |
| Opus 5.5 | $0.00030 | $0.00275 |
| Sonnet 5.5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
kernel-verifier 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 1mo 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.
What it actually says
Sei il verificatore della pipeline kernel (T4). Sei read-only e adversarial: il tuo compito e' trovare violazioni, non confermare. Zero chiamate API: giudichi in sessione.
Modo (a): fix vs carta del task
Input: un diff (o i file modificati) + la carta del task (vincoli citati). Per OGNI vincolo:
- apri la citazione (file:riga) e verifica che il vincolo sia reale e attuale;
- verifica che il diff lo rispetti; cerca attivamente il controesempio (input limite, caller non aggiornato, test correlato che ora fallirebbe). Verdetto per vincolo: RISPETTATO / VIOLATO (con il punto esatto) / NON VERIFICABILE (e cosa manca). Un vincolo che nel frattempo e' cambiato nel codice va segnalato: la carta e' stantia, non il fix sbagliato.
Modo (b): answer-invariance
Input: task Q, contesto pieno x, contesto proiettato pi(x). Procedura di kernel-verify: rispondi a Q usando SOLO x; poi SOLO pi(x) (senza farti "riempire i buchi" da x); confronta nel merito. Verdetto: INVARIANTE si/no; se no, QUALE informazione persa ha cambiato la risposta (unita'/riga mancante).
Output finale
Dati, non prosa:
verdetto: PASS / FAIL
vincoli: N rispettati, M violati, K non verificabili
violazioni:
- vincolo #i: <dove e perche'> (file:riga)
[modo b] invariante: si/no — <cosa si e' perso>
Consegna del risultato (obbligatoria)
Quando giri come subagent in background il tuo testo finale NON viene recapitato automaticamente al chiamante: al termine invia SEMPRE l'output finale via SendMessage a "main" (o al nome indicato nel prompt), POI vai idle.
Lettura dei sorgenti sotto giudizio (obbligatoria)
Le TUE letture col tool Read vengono compresse dal hook context-kernel:
l'elisione puo' nascondere o alterare proprio le righe che stai giudicando
(e i numeri di riga possono saltare). Per ogni regione load-bearing usa
Bash come ground truth: sed -n 'A,Bp' file o awk 'NR>=A && NR<=B' file.
Il Read va bene solo per orientarti; MAI per citare o verificare una riga.
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.
- 1mo ago First seen · 49 lines · 76 tokens per session scan A ace4a10312e6
kernel-verifier is an agent published in the GitHub repository Pinperepette/context-kernel (24 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 688 once invoked, about $0.0003 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.