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/OdinMB/ops-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/commands/odinmb/ops-workflow/recap)<a href="https://agentmods.dev/commands/odinmb/ops-workflow/recap"><img src="https://agentmods.dev/badge/commands/odinmb/ops-workflow/recap/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/commands/odinmb/ops-workflow/recap"><img src="https://agentmods.dev/badge/commands/odinmb/ops-workflow/recap.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.00105 | $0.01339 |
| Opus 5.5 | $0.00042 | $0.00536 |
| Sonnet 5.5 | $0.00021 | $0.00268 |
| Haiku 4.5 | $0.00011 | $0.00134 |
Grade A, and why
recap 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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize what happened in this project since the date specified: $ARGUMENTS
If no date is provided, ask the user for one.
Instructions
1. Parse the Date
Convert $ARGUMENTS to an absolute date (YYYY-MM-DD). Handle natural language like "last week", "March 1", "two weeks ago", "Monday". If the input is ambiguous or missing, ask the user.
Store the resolved date as $SINCE.
2. Gather Evidence
Collect changes from these sources. Read them in parallel where possible. Skip sources that don't exist.
a. Completed Plans
Read plans/completed/INDEX.md. Identify plans with date prefixes >= $SINCE. Read each matching plan file — focus on the Objective, Outcome, Key Decisions, and Artifacts sections.
b. Active Plans
Glob plans/*.md and skip INDEX.md — every other file directly under plans/ is an active plan (plans/INDEX.md deliberately lists none of them). Note any that were created after $SINCE (check their date prefix or file modification context). These represent work that started but hasn't finished yet.
c. Git History
Run git log --oneline --after=$SINCE to see commits in the date range. This captures changes that might not have corresponding plans (quick fixes, direct updates, autonomous work).
d. State File Changes
Grep all files under state/ for _Last updated: lines. Flag any with dates >= $SINCE — these represent reality that changed during the period.
e. New Artifacts
Scan artifacts/ (and subfolders) for files with date prefixes >= $SINCE. These are deliverables produced during the period.
f. MEMORY.md Changes
Check git log for commits that touched MEMORY.md since $SINCE. If any exist, note what Key Learnings or context was added.
g. Backlog Movement
Compare the current backlog state against git history to identify items that were added or removed since $SINCE. Use git log --oneline --after=$SINCE -- backlog/ to approximate this.
3. Assess Volume and Set Granularity
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.
- 12d ago Changed 6a8ef2aa150e
- 1mo ago First seen · 136 lines · 105 tokens per session scan A 1937cb546497
recap is a command published in the GitHub repository OdinMB/ops-workflow (7 stars, last pushed 13d ago), licensed MIT. It adds 105 tokens to every session and 1,339 once invoked, about $0.0004 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 commands, from other repositories
close
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
entry
Load a Linear issue into context and enter plan mode for a focused session.
submit
Move the current branch's Linear issue to In Review.
setup-linear
Configure .factory-kit/linear.json for the portable Linear workflows.
standup
Dev standup — open Linear tickets grouped by in-flight, top priority, and backlog.
forge-status
Show registry of all managed projects with scores, trends, and alerts.