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/docdyhr/simplenote-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/docdyhr/simplenote-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/docdyhr/simplenote-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/docdyhr/simplenote-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/docdyhr/simplenote-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 | $0.00611 | $0.00611 |
| Opus 5 | $0.00305 | $0.00305 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
simplenote-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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Code Generation Instructions
When generating code for this repository, follow these formatting rules:
Python Standards
- Formatting: Use Ruff formatter defaults (88 char line length, Black-compatible)
- Style: Follow PEP 8 with Ruff's opinionated style
- Imports: Sort imports with standard → third-party → local order
- Type Hints: Add type hints for all function parameters and returns
- Docstrings: Use Google-style docstrings for all public functions and classes
- Quotes: Prefer double quotes for strings (Black/Ruff default)
File Standards
- Line Endings: Always end files with a newline character
- Whitespace: Never include trailing whitespace
- Indentation: Use 4 spaces for Python, 2 for YAML/JSON, consistent throughout
Pre-commit Compliance
Generated code must pass these checks:
- ruff: Python linting and auto-fixes
- ruff-format: Code formatting (Black-compatible)
- mypy: Type checking (when type hints are used)
- trailing-whitespace: No trailing spaces
- end-of-file-fixer: Files end with newline
- check-yaml: Valid YAML syntax
- check-toml: Valid TOML syntax
Common Anti-patterns to Avoid
- F401: Don't import unused modules
- E402: Keep all imports at the top of files
- F841: Don't create unused variables
- B007: Use
_prefix for unused loop variables - E722: Don't use bare
except:clauses - B904: Use
raise ... fromin exception handlers
Specific Rules
- Keep line lengths under 88 characters for code, 80 for documentation
- Use f-strings for string formatting (except in logging)
- Prefer specific exception types over general
Exception - Use
Optional[Type]for nullable parameters - Add meaningful error messages to exceptions
- Include contextual information in log messages
Example Good Code
from typing import Optional
import logging
def process_note(note_id: str, content: Optional[str] = None) -> bool:
"""Process a note with optional content update.
Args:
note_id: The unique identifier for the note
content: Optional new content for the note
Returns:
True if processing succeeded, False otherwise
Raises:
ValueError: If note_id is empty or invalid
"""
if not note_id.strip():
raise ValueError("Note ID cannot be empty")
try:
# Process the note
return True
except Exception as e:
logging.error("Failed to process note %s: %s", note_id, e)
raise ProcessingError("Note processing failed") from e
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.
- 5d ago First seen · 80 lines · 611 tokens per session scan A 7c26c01ca8d7
simplenote-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository docdyhr/simplenote-mcp-server (19 stars, last pushed 2d ago), licensed MIT. It adds 611 tokens to every session, about $0.0031 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
wesight AGENTS.md
Instructions for freestylefly/wesight, covering claude.md, build and development commands, build production bundle (typescript + vite), lint with eslint and run memory extractor tests (node.js built-in test runner).
cship CLAUDE.md
Instructions for stephenleo/cship, covering cship — ai agent instructions, environment quirks, non-negotiable code patterns, before submitting a pr and project structure.
Claude-PHP-SDK copilot-instructions.md
Instructions for claude-php/Claude-PHP-SDK, covering copilot instructions for claude php sdk, project goals, architecture & core components, directory structure (to be created) and key architectural patterns.
trufos typescript-react-electron.instructions.md
TypeScript, React, and Electron coding standards for the Trufos project.
contexture cpp.instructions.md
Instructions for AcKeskin/contexture, covering cpp rules, c++ concurrency, c++ const-correctness, c++ error paths and c++ gpu interop.
contexture rust.instructions.md
Instructions for AcKeskin/contexture, covering rust rules, rust dependability and debug, rust documentation, rust error handling and rust flexibility.