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/hitmandark07/neatcodeai/verifyingnpx skills add HITMANdark07/neatcodeai --skill verifyinggit clone --depth 1 https://github.com/HITMANdark07/neatcodeaiWhat 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.00041 | $0.01451 |
| Opus 5 | $0.00020 | $0.00726 |
| Sonnet 5 | $0.00008 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
verifying 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 yesterday.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
Overview
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
This skill calls the validate_diff MCP tool as part of the completion gate. Tests passing is necessary but not sufficient — the change must also clear the repo's captured rules.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE FROM BOTH GATES
If you haven't run BOTH (a) the test command AND (b) validate_diff in this message, you cannot claim the change is done.
The Two Gates
A change is complete only when both of the following return clean in this turn:
Gate (a): Tests pass
- Run the project's test command for the affected files (or the whole suite if scope is unclear)
- Confirm exit code 0, zero failing assertions, no warnings beyond the project baseline
Gate (b): validate_diff returns clean
- Call the
validate_diffMCP tool withchanges: [{file, new_content}, ...]for every file you intend to claim is done - Confirm
violationsis the empty array - If violations come back, DO NOT claim done. Hand off to the
validating-diffskill to resolve them via the four-option UX (exception_once,exception_until,supersede,abort).
Both gates run on the SAME change set in the SAME turn. Tests passing yesterday plus a clean validate_diff from earlier today is not sufficient — the world may have moved.
The Gate Function
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves gate (a)? What changes are passed to gate (b)?
2. RUN GATE (a): Execute the FULL test command (fresh, complete)
3. RUN GATE (b): Call validate_diff with the change set
4. READ: Full output of both, check exit code, count test failures, inspect violations array
5. VERIFY: Do both outputs confirm the claim?
- If EITHER fails: state actual status with evidence; do not claim done
- If BOTH pass: state claim WITH evidence (test summary + "validate_diff: clean")
6. ONLY THEN: Make the claim
Skip any step = lying, not verifying
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.
- yesterday First seen · 168 lines · 41 tokens per session scan A 6e20545b453f
verifying is a skill published in the GitHub repository HITMANdark07/neatcodeai (0 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 1,451 once invoked, about $0.0002 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-31.
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…