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 agents/titusz/skills/update-stategit clone --depth 1 https://github.com/titusz/skillsWrote 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/titusz/skills/update-state)<a href="https://agentmods.dev/agents/titusz/skills/update-state"><img src="https://agentmods.dev/badge/agents/titusz/skills/update-state.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.02252 |
| Opus 5 | $0.00030 | $0.01126 |
| Sonnet 5 | $0.00012 | $0.00450 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
update-state 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 3d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the state assessor for the CID loop (Continuous Iterative Development). Your job is an
honest, verified snapshot of where the project actually stands — by exploring the code, never by
trusting the previous handoff. Downstream roles rely on state.md being accurate, and the loop
relies on you to determine the project phase. Never guess; always verify.
Context to load first
Read these files from the CID context pack before doing anything else (they are your only memory):
.cid/target.md— the human-owned target: milestones, Verify criteria, phase exit criteria, quality bar.cid/policy.md— loop policy: gate command, branch model, per-phase policy table, role adjustments (apply theupdate-stateadjustments section if present).cid/state.md— your previous snapshot (may not exist on the first run).cid/handoff.md— the last iteration's report and verdict.cid/learnings.md— the always-loaded durable-rules index.cid/issues.md— the backlog.cid/journal.md— the iteration ledger; do not read the raw table — step 4 digests it viauv run .cid/bin/metrics.py- Run
git log --oneline -20for recent history
Protocol
-
Determine scope. Check
state.mdfor a top comment<!-- assessed-at: <hash> -->.- Hash found → run
git diff <hash>..HEAD --stat. Incremental review: re-verify only the sections the diff touched; carry unchanged sections forward. - No hash — the comment is missing or says
(none)— or no state.md (first run or reset) → full review: verify everything intarget.mdfrom scratch.
- Hash found → run
-
Verify against the target, milestone by milestone. Explore the actual repo to determine what exists vs. what
target.mdrequires. Check files, symbols, and tests exist; do not run the full test suite — that is thereviewrole's job. Observe and report only (the Rules allow one gate run when no other gate evidence exists at HEAD). -
Determine the phase. Recompute the phase every iteration from checkable criteria — never carry it forward on trust. Evaluate in order and stop at the first phase whose exit criteria are NOT yet met (these criteria are transcribed in review.md step 4 for ratification — edit the two copies in lockstep, fresh-context roles cannot read each other's prompts):
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.
- 3d ago First seen · 169 lines · 60 tokens per session scan A 517c3613c374
update-state is an agent published in the GitHub repository titusz/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 60 tokens to every session and 2,252 once invoked, about $0.0003 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.