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 agentmods add skills/kenn-io/kata/verifynpx skills add kenn-io/kata --skill verifygit clone --depth 1 https://github.com/kenn-io/kataWrote 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/kenn-io/kata/verify)<a href="https://agentmods.dev/skills/kenn-io/kata/verify"><img src="https://agentmods.dev/badge/skills/kenn-io/kata/verify.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00412 |
| Opus 5 | $0.00009 | $0.00206 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
verify 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 4d 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
Verifying kata changes
Build
go build -tags kit_posthog_disabled -o /tmp/kata-verify ./cmd/kata
CLI surface (cmd/kata)
- Piped (must be ANSI-free):
/tmp/kata-verify list --limit 3 | cat -v - TTY-colored: run inside the tmux session below and capture with
-e.
TUI surface (internal/tui)
The TUI requires a real pty; use an isolated tmux socket. A local
daemon must be reachable (any workspace-bound directory works; the
repo itself is bound to the kata project).
tmux -L kataverify new-session -d -s v -x 120 -y 32
tmux -L kataverify send-keys -t v "cd <repo> && /tmp/kata-verify tui" Enter
sleep 3
tmux -L kataverify capture-pane -t v -p # plain frame
tmux -L kataverify capture-pane -t v -e -p # with ANSI, for color checks
Flows worth driving: Enter (detail), Esc (back), L at ≥140 cols
(split layout), resize below 80 cols (too-narrow hint), / + text
(search bar), q (quit modal) then n, ctrl+c (fast quit — pane must
return to shell with no leftover alt-screen garbage).
Teardown: tmux -L kataverify kill-server
Gotchas
tmux resize-window -t v -x <cols> -y <rows>exercises WindowSizeMsg handling live.- Golden snapshots (
testdata/golden/) are plain text; the test harness strips ANSI, so style-only changes don't churn them.
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.
- 4d ago First seen · 46 lines · 18 tokens per session scan A 4558b9fdd7b7
verify is a skill published in the GitHub repository kenn-io/kata (412 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 412 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…