recap

recap is a command for Claude Code from eddiebelaval/squire. It costs 0 tokens per session (362 once invoked), scanned A, original, MIT.

A weekly project-review command that compares the week's results with commitments made on Monday. It marks each commitment as done, partial, or missed and records the recap.

In plain words
What is it for?
Use it to review commitments, check signups, published content, and merged pull requests, and carry important unfinished work into the next week.
Why use it?
It makes unfinished work and actual progress visible instead of relying on memory or vague status updates.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to review commitments, check signups, published content, and merged pull requests, and carry important unfinished work into the next week.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/eddiebelaval/squire/recap
Install

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.

Clone the repo
git clone --depth 1 https://github.com/eddiebelaval/squire

Made for: Claude Code.

Wrote 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.

agentmods badge for recap

README.md
[![agentmods](https://agentmods.dev/badge/commands/eddiebelaval/squire/recap/github.svg)](https://agentmods.dev/commands/eddiebelaval/squire/recap)
Your own site
<a href="https://agentmods.dev/commands/eddiebelaval/squire/recap"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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.

agentmods 80×15 button for recap

Your own site · 80×15
<a href="https://agentmods.dev/commands/eddiebelaval/squire/recap"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 362 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00362
Opus 5 $0.00000 $0.00181
Sonnet 5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

Measured 5d ago against content hash 01628249013b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 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.

commands/recap.md · 55 lines

What it actually says

/recap - Friday Weekly Recap (5 min)

Score the week against Monday's war room commitments.

Process

  1. Find this week's war room file:
# Find the most recent Monday's war room file
ls ~/Development/id8/war-room/*.md 2>/dev/null | tail -1
  1. Read the file. Extract the Commitments section and The One Thing.

  2. For each commitment, score it:

    • DONE — Shipped, merged, sent, or completed
    • PARTIAL — Started but not finished
    • MISSED — Didn't happen
  3. Score The One Thing separately (this is the headline).

  4. Pull quick metrics to compare against Monday's scorecard:

    • Any new signups?
    • Any content published?
    • Any PRs merged?
  5. Append to the war room file:

## Friday Recap — [date]

### The One Thing: [DONE/PARTIAL/MISSED]
[One line on what happened]

### Commitments
- [x] Commitment 1 — DONE
- [ ] Commitment 2 — MISSED (reason)
- [~] Commitment 3 — PARTIAL (what's left)

### Week Score: [N]/[total] commitments done

### Carry Forward
- [Anything that missed and still matters]

### Wins
- [Best thing that happened this week, even if unplanned]
  1. Update session-log.md with recap summary.

Rules

  • Be honest. MISSED means missed. Don't soften it.
  • Carry forward is mandatory for missed items. They don't disappear.
  • Wins section exists because momentum matters. Always find at least one.
Changes

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.

  1. 5d ago First seen · 55 lines · 0 tokens per session scan A 01628249013b

Subscribe to this mod's changes

recap is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 362 tokens. 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.