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/brolag/neural-claude-code/vetnpx skills add brolag/neural-claude-code --skill vetgit clone --depth 1 https://github.com/brolag/neural-claude-codeWrote 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/brolag/neural-claude-code/vet)<a href="https://agentmods.dev/skills/brolag/neural-claude-code/vet"><img src="https://agentmods.dev/badge/skills/brolag/neural-claude-code/vet.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.00076 | $0.01357 |
| Opus 5 | $0.00038 | $0.00678 |
| Sonnet 5 | $0.00015 | $0.00271 |
| Haiku 4.5 | $0.00008 | $0.00136 |
Grade A, and why
vet 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vet
Review the change as an evaluator with no stake in shipping it. Report material findings only and return exactly SHIP or HOLD.
This skill is the Claude Code port of the Neural Codex vet gate. Same contract, slash invocation. The default independent reviewer is a fresh Agent. Codex is optional.
1. Resolve the target
Accept:
--base <ref>for a branch diff--scope working-tree|branch|pr--pr <number>and optional repository--spec <path>for acceptance criteria- trailing text as a review focus
Inspect status, branch, remotes, and the narrow project guidance relevant to touched files. If no diff or changed artifact exists, report that there is nothing to vet and stop.
BRANCH=$(git branch --show-current)
if [ "$BRANCH" != "main" ] && [ "$BRANCH" != "master" ]; then
git diff --stat main...HEAD && git diff main...HEAD
else
git diff --stat && git diff
fi
Honor --base / --scope if given.
2. Build a neutral review bundle
Create a temporary directory outside the repository and collect:
- objective and acceptance criteria from the plan
- base/head refs and target label
- status, tracked diff, staged diff, and diff stat
- an
untracked-manifest.txtgenerated fromgit ls-files --others --exclude-standard -z - tests already reported by the implementer
- relevant project constraints
- no authoring narrative, praise, or proposed verdict
Input hygiene (non-negotiable). Pass the bundle and a neutral focus string. Do not prepend a narrative that explains, motivates, or justifies the change.
For every untracked status entry, resolve it beneath the repository and account for it in the manifest. Copy safe text files into an untracked/ subtree that preserves relative paths. For directories, inventory their files recursively without following symlinks. For large, binary, ignored, sensitive, or excluded files, record path, size, hash when safe, and the reason content was omitted. The reviewer must compare the manifest with status before issuing a verdict. An unexplained missing path prevents SHIP.
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 · 141 lines · 76 tokens per session scan A 0439eaf6eb1c
vet is a skill published in the GitHub repository brolag/neural-claude-code (11 stars, last pushed 14d ago), licensed MIT. It adds 76 tokens to every session and 1,357 once invoked, about $0.0004 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…