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/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/post-cold-start-verification)<a href="https://agentmods.dev/commands/kunalsuri/ai-fication-kit/post-cold-start-verification"><img src="https://agentmods.dev/badge/commands/kunalsuri/ai-fication-kit/post-cold-start-verification/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/kunalsuri/ai-fication-kit/post-cold-start-verification"><img src="https://agentmods.dev/badge/commands/kunalsuri/ai-fication-kit/post-cold-start-verification.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.00025 | $0.00489 |
| Opus 5.5 | $0.00010 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
post-cold-start-verification 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 28d 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
Audit the AI knowledge layer. Read-only with one exception: you may write ONE report.
Step 0 — use the mechanical verifier's output, don't redo its job
If ai/analysis/audit-reports/VERIFICATION_MANIFEST.json exists, read its summary
and the non-confirmed claims first: path-existence checking is already done
deterministically by the kit's verify command (run from the kit checkout:
node install.mjs verify <repo> — no LLM
involved, so its statuses are facts). Spend your pass on what a script cannot
judge (checks 1, 3, 4 below, and the semantic half of check 2). If the manifest
is absent or older than the docs it covers, recommend regenerating it in your
report instead of re-deriving path checks by hand.
Checks
- Placeholders: find every
<fill in>,?Stability, and{{...}}leftover acrossai/and the entry files (CLAUDE.md, AGENTS.md). - Internal consistency: every path mentioned in
ai/guide/*exists on disk (covered by the manifest when present — see Step 0); MODULE_MAP rows correspond to real directories; FEATURE_MAP entries point at real files; diagrams name real modules. - Profile consistency: build/test commands in CLAUDE.md/AGENTS.md match
ai/repo-profile.json; flag divergence (don't silently fix). - Provenance hygiene: no
[verified]tag lacking a date; nothing you can tell was agent-written carrying[verified].
Output
Write ai/analysis/audit-reports/<YYYY-MM-DD>-post-cold-start.md: findings grouped
P1 (agent-blocking) / P2 (misleading) / P3 (cosmetic), each with location and a
one-line suggested fix. Tag the report itself [inferred]. Do not modify the files
you are auditing.
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.
- 28d ago First seen · 36 lines · 25 tokens per session scan A d63179c5a01d
post-cold-start-verification is a command published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 489 once invoked, about $0.0001 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-09-18.
Other commands, from other repositories
terse
Switch reply compression level — /terse [lite|full|ultra|off]. Complements RTK (input savings) with output-side savings.
start
Start a session — load context + memory and brief yourself on current state.
update
Mid-session checkpoint — save progress without ending the session.
motion
Motion work is applied within whatever component/section/page workflow is already running. If motion is the entire ask with nothing else changing, this command's steps above are sufficient on their own.
typography
This command is a lookup + decision, not a multi-step build — it doesn't need its own workflow file. If the request grows into "and now build the page using this type system," hand off to page or redesign.
cluster-instincts
Group related instincts by tag overlap and batch-promote qualifying clusters to skills. Usage - /mindforge:cluster-instincts [--dry-run] [--min-cluster 3] [--min-confidence 0.7].