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 agentmods add instructions/viitorohit/sitrep/claude-mdgit clone --depth 1 https://github.com/viitorohit/sitrepWhat 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 | $0.02024 | $0.02024 |
| Opus 5 | $0.01012 | $0.01012 |
| Sonnet 5 | $0.00405 | $0.00405 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
sitrep CLAUDE.md 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — sitrep Project
Project Overview
sitrep is an open-source AI-native project operations framework — the operations, cost, and continuity layer for AI-assisted development. It lives inside developer repos as markdown files that AI coding assistants read and update. It sits BESIDE planning tools (Jira, OpenSpec, Spec Kit), it does not replace them.
GitHub: github.com/viitorohit/sitrep · Domain: getsitrep.dev · License: MIT Shipped: v0.3.0 "Sharper & Self-Sufficient" (npm + GitHub release, 2026-07-08) · In development: v0.4.0 "Cost-to-Outcome & Beside"
Sources of Truth — Priority Order
- Jira project GETSITREP — canonical for scope, status, build order. Atlassian MCP is connected — fetch live rather than asking the session owner to paste.
- This repo,
docs/specs/— canonical for technical specs (command canon, adapter contract, cost schema), as they're authored. Confluence is a mirror of this, not the source (flipped 2026-07-03 — see ADR index below; specs not yet migrated are still Confluence-only until their owning Story authors thedocs/specs/version as part of its acceptance criteria). docs/adr/— canonical for why a decision was made. Immutable once Accepted; only ever superseded, never edited. Read the relevant ADR instead of asking "why" — don't re-litigate a decision that already has one.- This file — durable operating rules only (governance, hard laws, pointers). No decision rationale lives here anymore — that's what ADRs are for. No file-tree snapshot either (previous versions drifted twice) — audit the actual tree yourself at session start (
ls,git status). sitrep/dogfood files — reconciled and actively maintained (STATUS_REPORT.md/PROJECT_PLAN.md/.sitrep-data.jsonviasession-end,dashboard.htmlfolded into the same commit per ADR-0007). Still worth a quickgit log/Jira cross-check at session start — this project has hit real drift before when a session skippedsession-end(see GETSITREP-54, and the Session 9 close-out incident insitrep/STATUS_REPORT.md's own log).
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.
- 3d ago First seen · 76 lines · 2,024 tokens per session scan A a5e0c33e0ae4
sitrep CLAUDE.md is an instructions file published in the GitHub repository viitorohit/sitrep (19 stars, last pushed 1mo ago), licensed MIT. It adds 2,024 tokens to every session, about $0.0101 per session on Opus 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-30.
Other instructions, from other repositories
mcp-server-excel coverage-prevention-strategy.instructions.md
Instructions for sbroenne/mcp-server-excel, covering generated surface coverage, contract change workflow, required checks and common incomplete changes.
my-claude-code-setup GEMINI.md
Instructions for centminmod/my-claude-code-setup, covering gemini.md, ai guidance, memory bank system, core context files and project overview.
mcp-server-excel mcp-llm-guidance.instructions.md
Instructions for sbroenne/mcp-server-excel, a project described as: Automate real Microsoft Excel with AI via MCP Server or CLI — Power Query, DAX, VBA, PivotTables, charts, and 326 operations.
cship CLAUDE.md
Instructions for stephenleo/cship, covering cship — ai agent instructions, environment quirks, non-negotiable code patterns, before submitting a pr and project structure.
agentic-workflow CLAUDE.md
Instructions for gtrabanco/agentic-workflow, covering claude.md, repository layout, working rules, authoring a skill and hand off, don't compose across a model/effort boundary.
Claude-Code-Promts-Skills CLAUDE.md
Instructions for Rtur2003/Claude-Code-Promts-Skills, covering claude.md, project overview, repository structure, file naming conventions and prompt structure standards.