Borrowing it
Nothing to install: this file belongs to dbl8005/sitrep-panel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dbl8005/sitrep-panel/main/AGENTS.mdgit clone --depth 1 https://github.com/dbl8005/sitrep-panelWrote 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/instructions/dbl8005/sitrep-panel/agents-md)<a href="https://agentmods.dev/instructions/dbl8005/sitrep-panel/agents-md"><img src="https://agentmods.dev/badge/instructions/dbl8005/sitrep-panel/agents-md/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/instructions/dbl8005/sitrep-panel/agents-md"><img src="https://agentmods.dev/badge/instructions/dbl8005/sitrep-panel/agents-md.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.01488 | $0.01488 |
| Opus 5.5 | $0.00595 | $0.00595 |
| Sonnet 5.5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
sitrep-panel AGENTS.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 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sitrep-panel
A live local HTML report you keep updated as you work. It lives at
.sitrep-panel/report/ inside whatever project you're invoked from, served
on localhost, and it live-reloads in the browser every time you update it —
the user never has to hit refresh.
This is not a hosted artifact. It never leaves the user's machine, needs no publish step, and works offline. Use it whenever the user wants to watch a task happen rather than read about it after the fact — they'll typically ask by name ("start a sitrep-panel", "/sitrep-panel") or describe wanting a "progress report", "status page", or "live doc" for a task.
Invocation
sitrep-panel [start | open | stop | archive] — default (no argument) is
start.
start(default) — scaffold a new report if none is active, or resume the active one. Always ends by printing the localhost URL prominently.open— just print the URL of the active report (start the server if it isn't running); never touches content.archive— move the current active report to.sitrep-panel/archive/<timestamp>-<slug>/and scaffold a fresh one. Use this when starting genuinely new, unrelated work rather than continuing the current task.stop— kill the background server. Content on disk is untouched;startoropenlater brings it back.
First run — scaffold
If .sitrep-panel/report/ doesn't exist yet in the current project:
- Create
.sitrep-panel/report/screenshots/. - Copy
assets/template.html(from this package's own directory) to.sitrep-panel/report/index.html. Replace{{TITLE}}with a short name for the task, and{{SUBTITLE}}with one line of context (what this report is tracking, and when it started). - Write
.sitrep-panel/report/meta.json:{"updated_at": "<current ISO-8601 UTC timestamp>"} - If the project is a git repo and
.sitrep-panel/is not already covered by.gitignore, append it — this is local scratch, not something to commit. Mention you did this; don't ask first, it's trivially reversible.
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 · 127 lines · 1,488 tokens per session scan A 22a460fb04ad
sitrep-panel AGENTS.md is an instructions file published in the GitHub repository dbl8005/sitrep-panel (20 stars, last pushed 2mo ago), licensed MIT. It adds 1,488 tokens to every session, about $0.0060 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.