Borrowing it
Nothing to install: this file belongs to MicSm/boffin. 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/MicSm/boffin/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/MicSm/boffinWrote 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/micsm/boffin/copilot-instructions)<a href="https://agentmods.dev/instructions/micsm/boffin/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/micsm/boffin/copilot-instructions/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/micsm/boffin/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/micsm/boffin/copilot-instructions.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.02542 | $0.02542 |
| Opus 5.5 | $0.01017 | $0.01017 |
| Sonnet 5.5 | $0.00508 | $0.00508 |
| Haiku 4.5 | $0.00254 | $0.00254 |
Grade A, and why
boffin copilot-instructions.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.
Copies of this mod
2 near-identical copies found in the catalogue:
- boffin CLAUDE.md — 100% identical, 0 lines differ
- boffin AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ParselFire Core Portable Routing Contract
ParselFire Core gives AI coding agents a small routed set of architectural guardrails instead of one large always-on rules dump.
Default Workflow
First match scope to the task, then pick the path:
- Focused change (the operator asked for a specific function, fix, or feature): stay inside that scope. Make only the change requested, apply the stage guidance to what you touch, and prove it with a check. Do not scan the whole file or build a file-wide ledger; turning a scoped coding task into a file-wide refactor breaks the task boundary and gets rejected.
- Open-ended refactor, cleanup, or review of existing code: run the two-pass audit below, scoped to what the task covers.
Two-pass audit (refactor / review / cleanup). Never fix while you are still searching; the first strong improvement you find is not the finish line.
Pass 1, Audit (read-only). Read the target across the task's scope. Walk stages S00 upward and emit a findings ledger that covers every in-scope stage, including stages with nothing to change. Do not edit anything in this pass. Use one row per finding:
path | stage | status | id | kernel | anchor | check
Columns: path the file touched; stage the S00-S06 stage; status todo,
done, or skip; id the kernel id; kernel what it requires in one phrase;
anchor the concrete code location the finding rests on; check the test or
lint that proves it.
statusis one oftodo,done,skip, and everyskipcarries a reason.- Record every fix you name while auditing as its own row with all fields
filled, and resolve it as
doneorskip:<reason>; never leave a fix you mentioned in reasoning off the ledger. skip:cleanmeans Pass 1 found nothing on that stage; every in-scope stage still gets a row, never an omitted one.- A finding you deliberately will not act on is
skip:<reason>whose reason names the blocking kernel (for example, keeping a genuine special case instead of flattening it), neverskip:clean. - A row recorded as
todoresolves only todone(with its check) orskip:<reason>; never downgrade atodotoskip:clean.
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 · 187 lines · 2,542 tokens per session scan A 5873fc36c0dc
boffin copilot-instructions.md is an instructions file published in the GitHub repository MicSm/boffin (37 stars, last pushed 2mo ago), licensed MIT. It adds 2,542 tokens to every session, about $0.0102 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).
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.