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 commands/lollipopkit/cc-plugins/cf-verifygit clone --depth 1 https://github.com/lollipopkit/cc-pluginsWhat 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.00021 | $0.01622 |
| Opus 5 | $0.00010 | $0.00811 |
| Sonnet 5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
cf-verify 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify a context-firewall SubResult.v1.
Arguments
$ARGUMENTS
Expected:
--result <file|json>(required)--risk low|medium|high(optional, default: medium)--out <path>(optional)
Steps
1) Resolve project root
- Run
pwdvia Bash and treat it as the project root directory.
2) Load SubResult JSON (--result)
- Extract the
--resultvalue from$ARGUMENTS. - If the
--resultvalue begins with{, treat it as inline JSON. - Otherwise treat it as a file path:
- If it is not absolute, resolve to an absolute path by joining with the project root.
- Read the file content via Read.
3) Parse SubResult.v1 JSON
- Parse the content as JSON.
- If invalid JSON or missing required fields, output a VerifyReport.v1 with:
task_id: "unknown"status: "failed"checked/passed/failedconsistent with 0 checksrecommendationtelling the user to provide a valid SubResult.v1
4) Determine sampling rate
- Use
--riskif provided; otherwise default tomedium. - Sampling rates:
- high: 0.30
- medium: 0.15
- low: 0.05
5) Select claims to verify (deterministic)
-
Flatten claims into a list in stable order:
- Iterate answers in order.
- Iterate claims in order.
-
For each claim, derive a stable
claim_id:- If
claim.claim_idexists and is non-empty, use it. - Else use
answers[<answer_index>].claims[<claim_index>].
- If
-
Determine N = ceil(total_claims * sample_rate).
- If
total_claims > 0, ensureN >= 1. - If
total_claims == 0, setN = 0.
- If
-
Select the first N claims from the flattened list.
6) Verify each sampled claim
For each selected claim, attempt to verify at least one evidence item.
General rules:
- Prefer verifying the first evidence item with a
line_rangelocator. - Treat a claim as passed if any evidence item can be verified and is consistent.
- Treat a claim as failed if:
- a verifiable locator is provided but the snippet contradicts the claim, or
- a quoted substring is provided but is not found in the referenced snippet.
- Treat a claim as partial (unverifiable) if all evidence locators are of types not supported in v1 verification.
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 · 181 lines · 21 tokens per session scan A f9bb50a14699
cf-verify is a command published in the GitHub repository lollipopkit/cc-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 1,622 once invoked, about $0.0001 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 commands, from other repositories
advisor
Get a second opinion from Codex (GPT-5) on your current plan, diff, or a specific question.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
constatar-run
Execute a constatar plan.toml and report grounded results.
constatar-audit
Audit a constatar run — conformance, health trends, cost.
constatar-verify
Verify a unit of work with grounded evidence via constatar.
remoto-status
Show the remote agent fleet: host health and all jobs with their states.