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-specgit 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.00018 | $0.00422 |
| Opus 5 | $0.00009 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
cf-spec 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
Generate a TaskSpec.v1 JSON template for the user to edit.
Arguments
$ARGUMENTS
Steps
- Parse arguments:
--id <task_id>(optional)--risk low|medium|high(optional, default: medium)--objective <text>(optional)
- Determine
task_id:
- If
--idis provided, use it. - Otherwise generate one using Bash:
date +%Y%m%dfor the dateuuidgen | tr -d '-' | cut -c1-6for a short suffix- Format:
cf-<YYYYMMDD>-<suffix>
- Determine
risk_level:
- Use
--riskif provided, else"medium".
- Determine
objective:
- If
--objectiveis provided, use it. - Otherwise set a generic placeholder string that the user should replace.
- Output TaskSpec JSON with:
version: "TaskSpec.v1"output_schema: "SubResult.v1"map_reduce.enabled: truecritic.enabled: trueconstraintsfilled with defaults- Include minimal schema-valid placeholders:
inputs: include a single placeholder input (e.g.{ "type": "file", "path": "<PATH>" }).questions: include a single placeholder question (e.g."<QUESTION>").
Output rules (MANDATORY)
- Output strict JSON only.
- Do not use markdown fences.
- Do not include any explanation text before or after the JSON.
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 · 55 lines · 18 tokens per session scan A d2155740fc8d
cf-spec is a command published in the GitHub repository lollipopkit/cc-plugins (7 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 422 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.