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.
npx skills add hams-ollo/zen-agent-skills --skill sitrepgit clone --depth 1 https://github.com/hams-ollo/zen-agent-skillsWrote 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/skills/hams-ollo/zen-agent-skills/sitrep)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/sitrep"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/sitrep/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/skills/hams-ollo/zen-agent-skills/sitrep"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/sitrep.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.00129 | $0.01409 |
| Opus 5.5 | $0.00052 | $0.00564 |
| Sonnet 5.5 | $0.00026 | $0.00282 |
| Haiku 4.5 | $0.00013 | $0.00141 |
Grade A, and why
sitrep 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sitrep
Report the state of one repository from what the repository itself records, so the answer to "where are we?" is something a command produced rather than something a session remembered. A status report written from memory goes wrong in both directions and nothing marks which way; this reads the tracked task files and says what they say.
This skill is a draft. It ships with no profile and reaches no adopter until it has been used
on real work and blessed, per the contribution bar in the target repository's AGENTS.md. It is
also being built in stages, and this body describes only what exists so far: what waits on you,
what is in flight, what is blocked, what changed since you last caught up, and the figures a
repository declares, each with its tier.
When to use
- Someone asks where a project stands, what is waiting on them, or what is blocked.
- You are about to summarise a repository's state and would otherwise do it from memory.
When not to use
- The question is about sessions, agents, skills used, or cost. That is
agent-observatory. - The repository has no task files and the question is about tasks. The board says so rather than inventing an answer, but there is nothing for it to report.
Procedure
- Run
scripts/sitrep.pyfrom anywhere inside the repository. It prints what waits on you, what is in flight, what is blocked, and what changed since you last caught up, each task naming its file. - Report what it printed, leading with what waits on the person. Quote the reason each task is
waiting (
open questionorneeds a human eye) and, for a blocked task, what it waits on. - If it printed a notice, report the notice.
no task trackingmeans the repository has no tracked.tasks/directory, not that nothing is waiting.
What it reads, and what it decides
| Waiting on you when | Blocked when |
|---|---|
the task's last ## Open question heading has no ## Decision heading below it |
its depends_on names a task with no file under .tasks/done/ |
any heading contains the words held open for a human eye |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 114 lines · 129 tokens per session scan A caddf6be5799
sitrep is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 129 tokens to every session and 1,409 once invoked, about $0.0005 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-10-22.
Other skills, from other repositories
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-workspace
Manage GSD workspaces — create, list, or remove isolated workspace environments.
gsd-inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
gsd-pause-work
Create context handoff when pausing work mid-phase.