Borrowing it
Nothing to install: this file belongs to briangmilnes/APAS-VERUS. 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/briangmilnes/APAS-VERUS/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/briangmilnes/APAS-VERUSWrote 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/briangmilnes/apas-verus/copilot-instructions)<a href="https://agentmods.dev/instructions/briangmilnes/apas-verus/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/briangmilnes/apas-verus/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.36544 | $0.36544 |
| Opus 5 | $0.18272 | $0.18272 |
| Sonnet 5 | $0.07309 | $0.07309 |
| Haiku 4.5 | $0.03654 | $0.03654 |
Grade A, and why
APAS-VERUS 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 3d 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 — 4,453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: APAS accept and // accept hole — add only when user explicitly requests globs: "src/**/*.rs" alwaysApply: true
Accept Hole Rule
Patterns that mark known verification gaps or expected failures must not be added unless the user explicitly instructs it.
Covered patterns
| Pattern | Purpose |
|---|---|
// accept hole |
Comment near external_body; Veracity treats as info |
accept(...) / proof { accept(cond); } |
APAS accept proof fn; replaces assume for intentional holes |
Rule
- DO NOT add these patterns proactively.
- DO NOT add them to silence verification errors or proof-hole reports.
- DO add them only when the user explicitly says to (e.g., "add accept hole", "mark as accepted", "add APAS accept").
Rationale
These annotations document known gaps. Adding them without explicit approval can hide real issues or mask incomplete verification.
When the user asks
If the user says "add accept hole", "mark as accepted", "APAS accept", or similar, add the requested annotation at the specified location.
Rule: .cursor/rules/apas-verus/chapter-standalone.mdc
description: Same-algorithm implementation files (StEph, MtEph, StPer) must not import specs/lemmas from each other globs: "src/Chap*/**/*.rs" alwaysApply: true
Implementation Files Stand Alone
Different implementations of the same algorithm (StEph, StPer, MtEph) must not import specs or lemmas from each other, unless the APAS textbook explicitly specifies that one builds on another.
Rule
XStEph.rs, XMtEph.rs, and XStPer.rs are sibling implementations of algorithm X. Each must be self-contained. A student reading one file should not need to open another to understand the specs and proofs.
Scope
- In scope:
BSTPlainStEphmust not import fromBSTPlainMtEphorBSTPlainStPer;MergeSortMtPermust not import fromMergeSortStPer; etc. - Out of scope:
BSTAVLimporting fromBSTPlainwhen APAS presents AVL as extending plain BST — that is a different algorithm building on another, not a variant implementation.
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.
- 3d ago First seen · 4,453 lines · 36,544 tokens per session scan A 0870c906ec8f
APAS-VERUS copilot-instructions.md is an instructions file published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 36,544 tokens to every session, about $0.1827 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-09-03.
Other instructions, from other repositories
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.
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).
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).
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.
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.