cf-verify

A verification command for a Context Firewall result, a structured summary that records claims and where their supporting evidence can be found. It samples those evidence locations and rereads only the referenced snippets.

In plain words
What is it for?
Verifying SubResult.v1 JSON files or inline results, selecting claims by risk level, and writing a verification report.
Why use it?
It checks whether summarized claims are supported without loading an entire large file or log again. It reports whether the result passes or needs correction.

Command

Install

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.

agentmods
npx agentmods add commands/lollipopkit/cc-plugins/cf-verify
Clone the repo
git clone --depth 1 https://github.com/lollipopkit/cc-plugins
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,622 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash f9bb50a14699, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/context-firewall/commands/cf-verify.md · 181 lines

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 pwd via Bash and treat it as the project root directory.

2) Load SubResult JSON (--result)

  • Extract the --result value from $ARGUMENTS.
  • If the --result value 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/failed consistent with 0 checks
    • recommendation telling the user to provide a valid SubResult.v1

4) Determine sampling rate

  • Use --risk if provided; otherwise default to medium.
  • 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_id exists and is non-empty, use it.
    • Else use answers[<answer_index>].claims[<claim_index>].
  • Determine N = ceil(total_claims * sample_rate).

    • If total_claims > 0, ensure N >= 1.
    • If total_claims == 0, set N = 0.
  • 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_range locator.
  • 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.

Read the full file on GitHub · 181 lines

Changes

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.

  1. 2d ago First seen · 181 lines · 21 tokens per session scan A f9bb50a14699

Subscribe to this mod's changes

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.