Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/neelprime/arbiterx/copilot-instructionsgit clone --depth 1 https://github.com/NeelPrime/arbiterxWrote 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/neelprime/arbiterx/copilot-instructions)<a href="https://agentmods.dev/instructions/neelprime/arbiterx/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/neelprime/arbiterx/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 | $0.00191 | $0.00191 |
| Opus 5 | $0.00096 | $0.00096 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
arbiterx 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.
What it actually says
Engineering Rules (ArbiterX)
All generated code must follow these rules:
Required
- Type hints on all function parameters and return values
- Error handling for all I/O operations (try/except or context managers)
- Named constants instead of magic numbers
- Input validation at function entry
- Context managers for files and connections (
with open(...)) - Functions under 30 lines
Forbidden
- No hardcoded secrets or API keys
- No bare except clauses
- No string formatting in SQL queries (use parameterized)
- No eval() or exec()
- No TODO/FIXME comments — implement fully or skip
- No functions longer than 30 lines
- No unused imports or commented-out code
Prefer
- Standard library over external dependencies
- Early returns over deep nesting
- Immutable data where possible
- Specific exceptions over generic ones
str.join()over string concatenation in loops
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 · 28 lines · 191 tokens per session scan A 4ecc85b4c0ca
arbiterx copilot-instructions.md is an instructions file published in the GitHub repository NeelPrime/arbiterx (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 191 tokens to every session, about $0.0010 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-31.
Other instructions, from other repositories
procoder tests.instructions.md
Instructions for azrtydxb/procoder, covering tests in procoder, every test carries its mutation, assertions, portability and fixtures.
procoder copilot-instructions.md
Instructions for azrtydxb/procoder, covering procoder, the contract, the work chain, which command, right now and what you talk yourself into.
procoder go.instructions.md
Instructions for azrtydxb/procoder, covering go in procoder, no silent green, p-control: the binary prints, the agent writes, paths and arguments and exit codes are the public interface.
procoder workflows.instructions.md
Instructions for azrtydxb/procoder, covering ci in procoder, pins, actions and honesty in a job.
sdlc-quality copilot-instructions.md
Instructions for zircote-plugins/sdlc-quality, covering copilot instructions for sdlc plugin, project overview, repository structure, key conventions and rfc 2119 terminology.
sdlc-quality AGENTS.md
Instructions for zircote-plugins/sdlc-quality, covering agents.md - openai codex guidelines, project identity, quick context, agent guidelines and 1. understand the domain model.