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 skills/rbah31/claude-code-workflow/update-briefsnpx skills add rbah31/claude-code-workflow --skill update-briefsgit clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote 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/skills/rbah31/claude-code-workflow/update-briefs)<a href="https://agentmods.dev/skills/rbah31/claude-code-workflow/update-briefs"><img src="https://agentmods.dev/badge/skills/rbah31/claude-code-workflow/update-briefs.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.00077 | $0.00822 |
| Opus 5 | $0.00039 | $0.00411 |
| Sonnet 5 | $0.00015 | $0.00164 |
| Haiku 4.5 | $0.00008 | $0.00082 |
Grade A, and why
update-briefs 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 5d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Briefs
You are updating the shared memory (briefs/) after a sprint. Your job is to keep all strategic agents informed of the current project state.
Step 1 — Determine current sprint
Find the latest sprint directory in tasks/sprints/ (highest number).
Step 2 — Read sprint outputs
Read ALL available sprint output files:
tasks/sprints/sprint-XX/plan.mdtasks/sprints/sprint-XX/build-output.mdtasks/sprints/sprint-XX/review-output.mdtasks/sprints/sprint-XX/fix-output.mdtasks/sprints/sprint-XX/redteam-output.md(if exists)tasks/sprints/sprint-XX/retrospective.md(if exists)
Also read the current briefs/project-state.md.
Step 3 — Update project-state.md
Overwrite briefs/project-state.md with:
# Project State
Last updated: [date] — Sprint [XX]
## Current state
[What the project does right now, what's deployed, what works]
## Last sprint summary
Sprint [XX]: [theme]
- Completed: [tasks done]
- Issues found: [critical/major from review]
- Tests: [passing/failing count if known]
## Open items
- [Deferred issues from review/fix]
- [Items added to backlog]
## Next priorities
- [What should be done next based on backlog + retro]
## Blockers (manual actions needed)
- [Things that require human intervention]
Step 4 — Update marketing-sync.md
Append to briefs/marketing-sync.md with user-facing changes only:
### Sprint [XX] — [Date]
**User-facing changes**:
- [New feature / fix visible to users]
**Messaging angle**: [How to communicate this]
**Not for marketing** (internal only):
- [Technical changes not relevant to users]
If the sprint had no user-facing changes, skip this step.
Step 5 — Update blockers.md
If any manual actions were discovered during the sprint (deploy steps,
config changes, external service setup), append to briefs/blockers.md.
Step 6 — Update decisions-log.md
Append technical decisions made during the sprint to briefs/decisions-log.md.
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.
- 5d ago First seen · 109 lines · 77 tokens per session scan A 3dbf742d7e5d
update-briefs is a skill published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 822 once invoked, about $0.0004 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 skills, from other repositories
agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist.
agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator.
agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
memory-management
AgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval, persistent storage, and semantic search capabilities for learning and knowledge management. Use when: need to store successful patterns, searching for similar solutions, semantic lookup of past work, learning from previous…
external-memory-plugin
Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an…