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/viitorohit/sitrepWrote 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/viitorohit/sitrep/capture)<a href="https://agentmods.dev/commands/viitorohit/sitrep/capture"><img src="https://agentmods.dev/badge/commands/viitorohit/sitrep/capture/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/viitorohit/sitrep/capture"><img src="https://agentmods.dev/badge/commands/viitorohit/sitrep/capture.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.00000 | $0.00191 |
| Opus 5.5 | $0.00000 | $0.00076 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
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 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.
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.
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 · 17 lines · 0 tokens per session scan A 7adf69cc041f
capture is a command published in the GitHub repository viitorohit/sitrep (19 stars, last pushed 3mo 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.
Other commands, from other repositories
project-status
Summarize the current state of this client project.
sync-todos-to-github
Convert TodoWrite task list to GitHub plan issue (triggers automation).
work
Start working on a GitHub issue — fetch context, create branch, plan solution, and optionally open a PR.
create-task
Create a GitHub issue with project board integration.
jira-create
Create a new Jira ticket using the Atlassian MCP server.
jira-comment
Add a comment to a Jira ticket using the Atlassian MCP server.