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/szaffarano/org-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/szaffarano/org-mcp-serverWrote 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/szaffarano/org-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/szaffarano/org-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/szaffarano/org-mcp-server/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.01781 | $0.01781 |
| Opus 5 | $0.00890 | $0.00890 |
| Sonnet 5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
org-mcp-server 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 6d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
org-mcp-server
org-mcp-server is a Rust Model Context Protocol (MCP) server for org-mode knowledge management. It provides search, content access, and note linking capabilities for org-mode files through the MCP protocol.
ALWAYS reference these instructions first and fallback to the CLAUDE.md file, search, or bash commands only when you encounter unexpected information that does not match the info here.
Working Effectively
Bootstrap and Build
- NEVER CANCEL builds or tests - they may take up to 90 seconds to complete
- Build the workspace:
cargo build-- takes ~47 seconds. NEVER CANCEL. Set timeout to 90+ seconds. - Release build:
cargo build --release-- takes ~47 seconds. NEVER CANCEL. Set timeout to 90+ seconds. - Run tests:
cargo test-- takes ~2 seconds, 36 tests. Safe timeout 30+ seconds. - Lint code:
cargo clippy-- takes ~11 seconds. Safe timeout 30+ seconds. - Format code:
cargo fmt-- takes <1 second. Always run before commits. - Check formatting:
cargo fmt --check-- takes <1 second.
Development Commands
- Run CLI tool:
cargo run --bin org-cli -- --help - Run MCP server:
cargo run --bin org-mcp-server(needs valid org directory) - Run examples:
cargo run --example <name>(examples inorg-core/examples/) - Test specific crate:
cargo test -p <crate-name> - Build specific crate:
cargo build -p <crate-name>
Validation
CRITICAL: Always Test These Scenarios After Changes
-
Build validation: Run
cargo buildand wait for completion (90+ seconds) -
Test validation: Run
cargo testand verify all 36 tests pass -
CLI validation: Test core CLI functionality:
cargo run --bin org-cli -- list --dir org-core/tests/fixtures cargo run --bin org-cli -- read --dir org-core/tests/fixtures sample.org cargo run --bin org-cli -- outline --dir org-core/tests/fixtures sample.org cargo run --bin org-cli -- element-by-id --dir org-core/tests/fixtures simple-123
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.
- 6d ago First seen · 215 lines · 1,781 tokens per session scan A 741374907de0
org-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository szaffarano/org-mcp-server (42 stars, last pushed 3d ago), licensed MIT. It adds 1,781 tokens to every session, about $0.0089 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
serena copilot-instructions.md
Copilot instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!
serena AGENTS.md
AGENTS.md instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.
chunkhound AGENTS.md
AGENTS.md instructions for chunkhound/chunkhound, covering chunkhound llm context, projectidentity, modificationrules, keycommands and development.
mcp-server-starrocks CLAUDE.md
Claude Code instructions for StarRocks/mcp-server-starrocks, covering claude.md, project overview, development commands, run the server directly for testing and run with test mode to verify table overview functionality.
IntelliConnect CLAUDE.md
Claude Code instructions for ruanrongman/IntelliConnect, covering claude.md, project overview, technology stack, build commands and backend (maven).
IntelliConnect AGENTS.md
AGENTS.md instructions for ruanrongman/IntelliConnect, covering repository guidelines, project structure & module organization, compiler & environment, build, test, and development commands and coding style & naming conventions.