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/qinxiangcao/qualifiedcprogramming/final-checknpx skills add QinxiangCao/QualifiedCProgramming --skill final-checkgit clone --depth 1 https://github.com/QinxiangCao/QualifiedCProgrammingWhat 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.00045 | $0.00302 |
| Opus 5 | $0.00023 | $0.00151 |
| Sonnet 5 | $0.00009 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
final-check 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 2d 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
Final Check
When to invoke
Only the main agent invokes this skill after the controller has completed final-apply; no subagent is created. If final-check fails and rollback succeeds, follow the controller action and perform final-apply again before another final-check.
A human starts the public boundary with the root uv/Python 3.12 environment. Here, main executes only the action argv beginning with the validated absolute sys.executable; it does not wrap final-check in uv again.
Broad purpose
Use the controller to recheck source seals, symbolic-execution freshness, the full Rocq check, manual routes, the three active libraries, forbidden lemmas, and by-product cleanup. The run finishes only after every item passes.
Required reading
Main does not need to read a group-worker or other subagent skill. The controller mechanically checks forbidden lemmas, proof structure, and source seals. Main only executes the complete invocation carried by the action.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 25 lines · 45 tokens per session scan A 2f16e4fee04f
final-check is a skill published in the GitHub repository QinxiangCao/QualifiedCProgramming (43 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 302 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.