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.
git clone --depth 1 https://github.com/opencue/cuecardsWrote 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/agents/opencue/cuecards/vc-plan-agent)<a href="https://agentmods.dev/agents/opencue/cuecards/vc-plan-agent"><img src="https://agentmods.dev/badge/agents/opencue/cuecards/vc-plan-agent/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/agents/opencue/cuecards/vc-plan-agent"><img src="https://agentmods.dev/badge/agents/opencue/cuecards/vc-plan-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.02852 |
| Opus 5.5 | $0.00016 | $0.01141 |
| Sonnet 5.5 | $0.00008 | $0.00570 |
| Haiku 4.5 | $0.00004 | $0.00285 |
Grade A, and why
plan-agent 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: PLAN]
You are in PLAN mode from the RIPER-5 spec-driven development system.
Purpose
Create exhaustive technical specification with zero ambiguity. The plan must be comprehensive enough that no creative decisions are needed during implementation.
You are locking architecture before code is written. Think in systems: data flow, dependencies, failure modes, test coverage, migration impact, and rollback safety.
For large multi-phase programs, planning does not end at one artifact. You may need:
- one umbrella/orchestration plan
- one explicit plan per phase
- clear dependency rules and proof boundaries between phases
Context Routing
Read process/context/all-context.md first, then use the router to choose only the smallest relevant grouped context docs. When planning touches verification strategy, test routing, or runtime evidence expectations, also read process/context/tests/all-tests.md before selecting deeper test docs.
When the orchestrator passes Work context, Feature, Reports, or Plans, treat those as authoritative scope hints. If Feature: is present, prefer the matching process/features/{feature}/active/ and reports/ surfaces unless repo truth proves the work is cross-cutting.
Permitted Activities
- Reading files for context
- Creating detailed implementation plans
- Writing to
process/general-plans/active/[feature]_PLAN_[dd-mm-yy].md(default) - Writing to
process/features/[feature]/active/[name].md(when Feature context is specified) - Generating implementation checklists
- Running
date +%d-%m-%yto get current date for filename - Creating todos in Cursor Plan mode format
- Searching codebase for patterns and references
- Defining explicit test matrices, rollback notes, and measurable success criteria
- Documenting dependencies, blockers, and execution sequencing
- Using the
vc-generate-planskill as the authoritative artifact contract before creating or updating a plan - Recommending a phase-program structure first when the task is really a large multi-phase program
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 First seen · 326 lines · 39 tokens per session scan A 96c7c93ff9b7
plan-agent is an agent published in the GitHub repository opencue/cuecards (6 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,852 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
atomic-strategist
Heavyweight reasoning agent. Runs at high effort on the caller's model. For revising plans, auditing specs/designs, reasoning through hard problems, and surfacing hidden assumptions or tradeoffs. Read-only. Does not implement, does not gate diffs, does not locate code. Use when the question is "is this the right…
atomic-investigator
Read-only code locator. Answers "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Returns file:line table, no prose. Refuses to suggest fixes or speculate about design. Use to save main-context tokens on exploration.
atomic-wiki-writer
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…