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 juxt/claude-plugins --skill sitrepgit clone --depth 1 https://github.com/juxt/claude-pluginsWrote 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/juxt/claude-plugins/sitrep)<a href="https://agentmods.dev/skills/juxt/claude-plugins/sitrep"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/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/juxt/claude-plugins/sitrep"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/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.00089 | $0.01687 |
| Opus 5.5 | $0.00036 | $0.00675 |
| Sonnet 5.5 | $0.00018 | $0.00337 |
| Haiku 4.5 | $0.00009 | $0.00169 |
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 11d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chalk Sitrep — Where the Session Has Got To
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
A sitrep is written for whoever picks the session up next — the user after a break, a future agent after a compaction, or the user's colleague reading over their shoulder. It is not a log of the session. It is the state the session has reached, and what still needs a decision.
$ARGUMENTS, if given, narrows the scope; report only on that and say in one line what you left out.
Before you write
-
Load
chalk:voice— the register, every parent a claim its children back up, and the typed-ID scheme the Open section runs on. -
Its register applies; its palette doesn't. A sitrep is a terminal reply, not a GitHub artefact: no sections drawn from the palette, and no self-ranking, no smoke, no mea culpas.
Ground the report before writing it
A sitrep that trusts the transcript reports intentions as achievements. The transcript records what was attempted; the repo records what happened.
-
Check the working tree —
git status,git diff --stat, andgit logback to where the session started. This is what settles the Done/Open boundary for anything touching code. -
Read the session's plan, where
chalk:pick-upstarted one. Where it and the transcript disagree, resolve the ambiguity. -
Re-read the artefacts the session claims to have produced where cheap — the file, the issue, the PR body. A file written three edits ago may not say what the session thinks it says.
-
Say so if the context was compacted. One line, at the top: the earlier part of the session is a summary, so coverage before that point is partial. The reader needs to know which half of the report is first-hand.
Section 1: Done
One bullet per change that actually landed, children carrying the specifics. The reader is reorienting, so they take subject lines and stop: each MUST be agreeable without its children, which for Done means it says what is now true rather than what was worked on. No IDs here — Done is not up for reply, and IDs on it are noise.
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.
- 11d ago Changed · +78 lines · -3 tokens per session 8dd8203720b6
- 13d ago Changed · -75 lines · +3 tokens per session 1ff79cf82521
- 1mo ago Changed · -16 lines d22c5052dfce
- 1mo ago Changed · +28 lines 9ab96f71dbef
- 1mo ago Changed · +4 lines bcf90b8f3602
- 1mo ago Changed · +2 lines 44ab7f71162f
- 1mo ago Changed · +3 lines 1090089f1949
- 1mo ago First seen · 100 lines · 89 tokens per session scan A 74bd5b1b1c23
sitrep is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,687 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…