Borrowing it
Nothing to install: this file belongs to a-Fig/Accordion. 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/a-Fig/Accordion/main/AGENTS.mdgit clone --depth 1 https://github.com/a-Fig/AccordionWrote 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/a-fig/accordion/agents-md)<a href="https://agentmods.dev/instructions/a-fig/accordion/agents-md"><img src="https://agentmods.dev/badge/instructions/a-fig/accordion/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/a-fig/accordion/agents-md"><img src="https://agentmods.dev/badge/instructions/a-fig/accordion/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.00391 | $0.00391 |
| Opus 5.5 | $0.00156 | $0.00156 |
| Sonnet 5.5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
Accordion 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.
What it actually says
Read the entirety of @CLAUDE.md
Worktree convention
Before making any changes to the code, always open a dedicated worktree — never edit in the main checkout.
- Create a worktree off the latest
devmain, placed under.pi/worktrees/(already gitignored):git fetch origin git worktree add .pi/worktrees/<short-descriptive> -b <branch> origin/devmain cd .pi/worktrees/<short-descriptive> - Do all work in the worktree — edits,
npm install(deps are per-worktree), verification (npm run check,npm run test,node smoke.mjs,npm pack --dry-runas applicable), commits, and the PR todevmain. - Delete the worktree and its folder once the branch is merged into
devmain(or promoted tomain):cd <main checkout> git worktree remove .pi/worktrees/<short-descriptive> git branch -d <branch> # safe once merged; use -D only if the branch was abandoned - Notes:
- The main checkout stays on
main(the stable, registered-binary surface). Never branch from or PR intomaindirectly — see CLAUDE.md → Branching & PR workflow. - Only one worktree may run the UI server on port 1420 at a time (
npm run dev/tauri dev). Other concurrent worktrees should rely onnpm run check/npm run test/node smoke.mjs, which claim no port. - If the branch is abandoned without merging, still
git worktree removeit so.pi/worktrees/doesn't accumulate stale trees.
- The main checkout stays on
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 · 24 lines · 391 tokens per session scan A 7dce15fe4986
Accordion AGENTS.md is an instructions file published in the GitHub repository a-Fig/Accordion (247 stars, last pushed 28d ago), licensed MIT. It adds 391 tokens to every session, about $0.0016 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.