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 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/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/skills/rbah31/claude-code-workflow/update-briefs"><img src="https://agentmods.dev/badge/skills/rbah31/claude-code-workflow/update-briefs.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.00077 | $0.00822 |
| Opus 5.5 | $0.00031 | $0.00329 |
| Sonnet 5.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 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 — 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.
- 1mo 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 4mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 822 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…
knowledge-curation
Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
backlog
Seed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an ordered list of feature-sized items each traced to a source section, the user edits the list, and on explicit confirmation each item is filed as a GitHub issue that /story-time can import. Use…
harness-step3-session-management
A project setup for keeping an agent’s work state in files between separate chat sessions. It creates a task list, a progress summary, and a script for checking the project environment.