capture

A command that records a new task in the project plan and status report. It assigns a task ID, adds the task to the appropriate section, and commits the update.

In plain words
What is it for?
Use it to capture tasks for the current phase or mark them as future work, with an optional explicit phase.
Why use it?
It keeps new work from being forgotten and avoids manually updating several project records.

Command for Claude Code

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.

agentmods
npx agentmods add commands/viitorohit/sitrep/capture
Clone the repo
git clone --depth 1 https://github.com/viitorohit/sitrep

Made for: Claude Code.

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 191 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00191
Opus 5 $0.00000 $0.00096
Sonnet 5 $0.00000 $0.00038
Haiku 4.5 $0.00000 $0.00019

Measured 2d ago against content hash 7adf69cc041f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

capture 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 2d 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.

.claude/commands/capture.md · 17 lines

What it actually says

Capture — Add Task to Plan & Status

Intentional (manually invoked).

Capture a new task into the project plan and status report in one step. Never lose an idea mid-session.

Thin wrapper (GETSITREP-10) — task-ID assignment, table insertion, and commit all live in getsitrep capture. No interactive "which phase?" prompt (unlike this command's original design) — a non-interactive CLI can't ask a question mid-session, so it silently defaults to STATUS_REPORT.md's Current Phase when --phase/--future are both omitted. Pass --phase N explicitly if that default is wrong.

Run:

getsitrep capture $ARGUMENTS

Examples: getsitrep capture "add export to PDF feature" --phase 3, getsitrep capture "refactor connection pooling" --future.

Print its output verbatim.

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. 2d ago First seen · 17 lines · 0 tokens per session scan A 7adf69cc041f

Subscribe to this mod's changes

capture is a command published in the GitHub repository viitorohit/sitrep (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 191 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-08-30.