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/plan-update)<a href="https://agentmods.dev/commands/viitorohit/sitrep/plan-update"><img src="https://agentmods.dev/badge/commands/viitorohit/sitrep/plan-update/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/plan-update"><img src="https://agentmods.dev/badge/commands/viitorohit/sitrep/plan-update.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.00451 |
| Opus 5.5 | $0.00000 | $0.00180 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
plan-update 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
Update Project Plan
Intentional (manually invoked).
Thin wrapper (GETSITREP-10) over getsitrep plan-update — the CLI owns the table lookup, row insertion, and commit. This file's only remaining job is the one step no CLI can do on its own: interpreting the free-form request in $ARGUMENTS into the structured JSON the CLI expects.
No PROJECT_PLAN.md yet? (GETSITREP-25 plan-presence guard)
If sitrep/PROJECT_PLAN.md doesn't exist, running getsitrep plan-update with no --data triggers a guard: interactively it asks to generate a draft from repo introspection, but an AI-driven invocation won't have a real TTY to answer that prompt — use the non-interactive form directly instead:
getsitrep plan-update --generate --brief "<one-line description, optional>"
This generates a draft from package.json/README.md/git config and writes it — safe to call, it never overwrites an existing plan. Skip Steps 1-2 below in this case.
Step 1: Interpret the request
Read $ARGUMENTS. Determine whether it describes a decision or a risk:
- Decision →
{"type": "decision", "decision": "...", "rationale": "...", "date": "YYYY-MM-DD"?}(dateoptional, defaults to today) - Risk →
{"type": "risk", "risk": "...", "impact": "High"|"Medium"|"Low", "mitigation": "..."}
If it's genuinely ambiguous which one applies, or a required field is missing from the request, ask the user rather than guessing.
Note: adding a task to a phase or the Future table is /capture's job, not this command's — if the request is really "add a task," say so and suggest /capture instead of forcing it into this shape.
Step 2: Call the CLI
getsitrep plan-update --data '<the JSON from Step 1>'
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 · 35 lines · 0 tokens per session scan A 3f05db554330
plan-update 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 451 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
writing:compound
Capture learnings from successful writing to improve future work.
project-status
Summarize the current state of this client project.
codex-exec
Easy wrapper for running Codex CLI commands from Claude Code with proper syntax.
pr
Create a pull request from the current branch.
sync-branch
Sync feature branch with the latest main branch.
test-factory
Quick testing helper for generated skills and agents to ensure they work correctly.