Borrowing it
Nothing to install: this file belongs to QinxiangCao/QualifiedCProgramming. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/QinxiangCao/QualifiedCProgramming/main/.agents/skills-en/vc-checking/SKILL.mdgit 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/vc-checking)<a href="https://agentmods.dev/skills/qinxiangcao/qualifiedcprogramming/vc-checking"><img src="https://agentmods.dev/badge/skills/qinxiangcao/qualifiedcprogramming/vc-checking/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/qinxiangcao/qualifiedcprogramming/vc-checking"><img src="https://agentmods.dev/badge/skills/qinxiangcao/qualifiedcprogramming/vc-checking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00095 | $0.00622 |
| Opus 5.5 | $0.00038 | $0.00249 |
| Sonnet 5.5 | $0.00019 | $0.00124 |
| Haiku 4.5 | $0.00010 | $0.00062 |
Grade A, and why
vc-checking 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 1mo 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VC Checking
You are the vc-checking owner for the current attempt and complete only VC analysis, grouping, and this delivery. Every attempt is a new independent session; rely only on the controller claim/handoff, the current agent_input.md, and files bound by the handoff. Do not depend on the parent transcript or speculate about or advance later annotation, group proving, merge, final apply, or other phases.
Reading order
- Read the VC analysis and grouping workflow in full. It is the process, write, command, and output contract for the current role.
- As required by the workflow, read the VC analysis guide and natural-language analysis. They provide proof-analysis knowledge only; if an obsolete process description in either document conflicts with the workflow, the workflow prevails.
- Read the
agent_input.mdnamed by the claim message in full, then read the current main-root formal files, listed earlier vc-checking results, and controller blocker.
The root AGENTS.md, orchestrator, another role's skill, controller state/events, and unlisted history are not inputs for this role and must not replace the current handoff. Accidentally reading an extra file is not itself a blocker; continue from the current manual unless an out-of-bound write or reliance on non-current content affects the delivery.
Delivery objectives
- Scan every top-level VC first, prioritizing no-split whole goals and missing resource-address, scalar-equality, or current/
@prebridges; a definite countermodel may return immediately. - Read annotation VC comparisons as priority review leads, then independently check every added-premise source and related VC in the current manual.
- When the structural scan finds no definite blocker, apply exhaustive split-first analysis and a unique
proof_modedecision to every top-level VC. - Write executable strategies only for the selected formal targets; do not analyze witness reuse.
- Assess risk and choose plan order yourself, grouping current/related VCs that need a new substantial mathematical lemma together where useful. The controller retains groups containing comparison
currentVCs as the first batch and uses plan order within each batch, without score-based reordering. - Write
agent_report.jsonlast, stop all writes, and return the delivery to main/controller;finalize-deliveryperforms complete report/plan acceptance; repairs stay within the same owner, attempt, and permitted boundary.
What ships with it
3 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.
- 1mo ago Changed · -1 tokens per session ec5df029a959
- 1mo ago Changed · +2 lines · +5 tokens per session 175180f552ef
- 2mo ago First seen · 24 lines · 91 tokens per session scan A dfb9cd9f09f9
vc-checking is a skill published in the GitHub repository QinxiangCao/QualifiedCProgramming (51 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 622 once invoked, about $0.0004 per session on Opus 5.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
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…