Borrowing it
Nothing to install: this file belongs to paulnsorensen/easy-cheese. 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/paulnsorensen/easy-cheese/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/paulnsorensen/easy-cheeseWrote 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/paulnsorensen/easy-cheese/copilot-instructions)<a href="https://agentmods.dev/instructions/paulnsorensen/easy-cheese/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/paulnsorensen/easy-cheese/copilot-instructions.svg" alt="Measured on agentmods" 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.00708 | $0.00708 |
| Opus 5 | $0.00354 | $0.00354 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
easy-cheese 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 7d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot review instructions — easy-cheese
This repo is a skills-only collection following the
Agent Skills spec. Every change either
adds, edits, or supports a skill under skills/<name>/. There is no
production runtime: review focuses on skill quality, not application
behavior.
When reviewing a PR, treat it the way the /skill-creator skill would: care
about whether the skill will trigger when it should, whether it teaches the
model why not just what, and whether bundled resources earn their keep.
What this repo is and isn't
- Is: self-contained
SKILL.mdfiles for shaping ideas, implementing them, and reviewing the result. Workflow skills (mold,culture,cook,press,age,cure,melt,cheese,briesearch) call source-code backends directly through the shared routing contract. - Isn't: an agent framework, an orchestrator, or a mandatory-MCP runtime. Native LSP/AST/anchored-edit backends may satisfy
skills/cheese/references/code-intelligence-routing.mdwithout a specific MCP. Keep this scope in mind — flag scope creep (intent classification baked into a workflow skill, multi-CLI fan-out inside a tool skill, implicit cross-skill invocation) at review time. Cross-skill handoffs belong in the README's "Suggested flow" or in the skill's own routing section, not as silent auto-dispatch.
Skill review priorities (in order)
Apply the path-scoped instructions in .github/instructions/ for the
specifics. The summary order:
- Triggering — does the description tell Claude when to use this skill, in language users actually type?
- Progressive disclosure — is
SKILL.mdlean? Does deeper material live inreferences/,scripts/,assets/instead of inline? - Why over what — does the skill explain reasoning, or just bark MUSTs?
- Bundled resources earn their keep — every
references/<file>.mdandscripts/<file>should have a clear pointer fromSKILL.mdtelling the model when to load or run it. - Anti-overfit — instructions generalize across realistic prompts, not just the examples baked into the skill itself.
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.
- 7d ago First seen · 59 lines · 708 tokens per session scan A bd461c5e586b
easy-cheese copilot-instructions.md is an instructions file published in the GitHub repository paulnsorensen/easy-cheese (18 stars, last pushed yesterday), licensed MIT. It adds 708 tokens to every session, about $0.0035 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.