Borrowing it
Nothing to install: this file belongs to robcsaszar/retrospective. 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/robcsaszar/retrospective/main/AGENTS.mdgit clone --depth 1 https://github.com/robcsaszar/retrospectiveWrote 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/robcsaszar/retrospective/agents-md)<a href="https://agentmods.dev/instructions/robcsaszar/retrospective/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/retrospective/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/robcsaszar/retrospective/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/retrospective/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.00750 | $0.00750 |
| Opus 5.5 | $0.00300 | $0.00300 |
| Sonnet 5.5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
retrospective 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Mission
This repo publishes the retrospective skill for others to install. There is no build, no tests, no runtime of its own; the deliverable is the contents of skills/retrospective/. Judge changes by one test: would a stranger who installs this skill into their own project get a correct, generically useful session review out of it — one grounded in the conversation they are actually in?
Judgment boundaries
NEVER:
- Never let the skill read an on-disk transcript, log, or exported chat — its whole premise is that the current conversation is already the context. A version that opens a file to score it is a different, more dangerous skill.
- Never let the skill fabricate token counts, tool calls, or quotes. Relative magnitude only; the account is grounded in what happened, not in invented numbers.
ASK:
- Ask before adding a second skill; this repo is intentionally single-skill.
- Ask before restructuring the shape → context → wiring flow, or removing the honesty rules (current-session-only, no fabrication, never block on I/O).
- Ask before changing the license or copyright holder.
ALWAYS:
- Keep the skill's content generic — it must read as session review guidance for any project on any Agent Skills host, never tied to one codebase, tracker, or tool's command names.
- Keep the six shape names, the five economy-rule names, and the score key consistent between
SKILL.mdand thereferences/files — the review cites them by name, so a rename in one place without the other breaks the citations.
Releasing
Releases are cut by the Release workflow (.github/workflows/release.yml), never by hand. It is a manual workflow_dispatch with one input, tag, and it releases the commit at the tip of the branch it is run on. Run it on main.
The workflow, in order:
- Rejects a tag that is not
vX.Y.Z, or that already exists. - Fails unless
versionin.claude-plugin/plugin.jsonandplugins[0].versionin.claude-plugin/marketplace.jsonboth equalX.Y.Z. - Takes the
## [X.Y.Z]block fromCHANGELOG.mdas the release notes, and fails if there is none. - Creates the tag at the checked-out commit and publishes the GitHub release with those notes.
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 Changed · +29 lines · +418 tokens per session 054ab25bf9ac
- 2mo ago First seen · 21 lines · 332 tokens per session scan A 6418d98e1de4
retrospective AGENTS.md is an instructions file published in the GitHub repository robcsaszar/retrospective (0 stars, last pushed 1mo ago), licensed MIT. It adds 750 tokens to every session, about $0.0030 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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.