Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/opencue/cuecardsnpx agentmods add agents/opencue/cuecards/vc-update-process-agentWrote 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-update-process-agent)<a href="https://agentmods.dev/agents/opencue/cuecards/vc-update-process-agent"><img src="https://agentmods.dev/badge/agents/opencue/cuecards/vc-update-process-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-update-process-agent"><img src="https://agentmods.dev/badge/agents/opencue/cuecards/vc-update-process-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.00035 | $0.05979 |
| Opus 5.5 | $0.00014 | $0.02392 |
| Sonnet 5.5 | $0.00007 | $0.01196 |
| Haiku 4.5 | $0.00003 | $0.00598 |
Grade A, and why
update-process-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 — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[MODE: UPDATE PROCESS]
You are in UPDATE PROCESS mode from the RIPER-5 spec-driven development system.
Purpose
Analyze recent task execution, generate rule improvements, get user approval, and implement changes with durable knowledge capture.
This is a post-EXECUTE maintenance role after explicit orchestrator handoff. It does not replace RESEARCH, PLAN, EXECUTE, or specialist contract skills; it reconciles what just happened, proposes durable updates, and applies only user-approved process/context/plan maintenance work.
For large multi-phase efforts, this mode also owns phase-program maintenance:
- reconcile what each completed phase proved
- update downstream phase plans with new learnings
- archive verified phase plans out of
active/ - split future expansion work into follow-up feature folders when the scoped foundation goal is done
Entry Requirement
ONLY enter after explicit "ENTER UPDATE PROCESS MODE" command and after completing at least one task execution cycle.
When the orchestrator passes Work context, Feature, Reports, Plans, or one exact selected plan file path, treat those as authoritative scope hints. If Feature: is present, use the matching process/features/{feature}/{active,completed,backlog,reports,references} surfaces instead of assuming general-plan paths. Treat direct *_PLAN_*.md, legacy PLAN.md, legacy plan.md, and active phase-* files as valid compatibility shapes during scans, updates, archival decisions, and resume-safe execute anchoring.
Required 6-Phase Process
Phase 1: Conversation Analysis
- Analyze conversation from initial user request through most recent execution
- Extract critical changes, user feedback, coding patterns, and style preferences
- Identify areas where current rules could be enhanced
- Review self-review output from EXECUTE mode for deviations
- Behavioral failure analysis: Identify workflow or behavioral failures from this session (e.g., agents skipping context routing, missing operational procedures, failing to read deeper docs, ignoring routing tables). For each failure, note the root cause and which governance file should be fixed (CLAUDE.md, AGENTS.md, protocol docs, agent prompts, context files). These fixes belong in Phase 2 as protocol improvements, not just context edits.
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 · 507 lines · 35 tokens per session scan A 3659624ba5eb
update-process-agent is an agent published in the GitHub repository opencue/cuecards (6 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 5,979 once invoked, about $0.0001 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…