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/group-worker-provingnpx skills add QinxiangCao/QualifiedCProgramming --skill group-worker-provinggit clone --depth 1 https://github.com/QinxiangCao/QualifiedCProgrammingWrote 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/qinxiangcao/qualifiedcprogramming/group-worker-proving)<a href="https://agentmods.dev/skills/qinxiangcao/qualifiedcprogramming/group-worker-proving"><img src="https://agentmods.dev/badge/skills/qinxiangcao/qualifiedcprogramming/group-worker-proving.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.00067 | $0.00430 |
| Opus 5 | $0.00034 | $0.00215 |
| Sonnet 5 | $0.00013 | $0.00086 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
group-worker-proving 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
Group Worker Proving
Role boundary
Use only the current claim/handoff, this skill, and its linked documents. Do not read the orchestrator or another role's skill, rely on a parent transcript, read or wait for a sibling group, dispatch another group, or perform merge, parent verify, or annotation retry.
Complete this group's top-level VCs and applicable split goals under the controller-validated proof_mode. Maintain proofs/helpers only in the fixed copies named by the handoff, use the handoff-rendered commands for optional preflight checks, then stop writing and deliver the report so the main agent can invoke finalize-delivery for sealing and validation.
When an annotation/spec gap is diagnosed, that gap is this group's terminal result: stop adding out-of-bound repairs to this group's copies, write a complete traceable blocker, and deliver normally. This worker does not use that result to decide, stop, or advance any other group or parent phase.
Required reading
- Always read Proof flow, Commands and checks, and Mandatory forbidden-lemma rules in full.
- Before proving a manual VC, read Whole separation-logic proof tactics.
- When this group contains a refinement target, read Refinement proof tactics.
- When this group uses ordering, bounds, sum, or another pure-proposition predicate, read Pure proposition proof patterns.
- Read Reference cases only when an analogous proof is genuinely needed.
What ships with it
7 files 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.
- 4d ago First seen · 23 lines · 67 tokens per session scan A a1c661a03752
group-worker-proving is a skill published in the GitHub repository QinxiangCao/QualifiedCProgramming (43 stars, last pushed 13d ago), licensed MIT. It adds 67 tokens to every session and 430 once invoked, about $0.0003 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…