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/alexanderwillner/things-mcp/copilot-instructionsgit clone --depth 1 https://github.com/AlexanderWillner/things-mcpWhat 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.00424 | $0.00424 |
| Opus 5 | $0.00212 | $0.00212 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
things-mcp 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 2d 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
Copilot Instructions
This project is a Python CLI application that runs a Model Context Protocol (MCP) Server for Things 3, enabling AI access to todos and projects.
Coding Standards
- Focus on code readability
- Divide code into smaller, self-contained modules or functions for reusability and maintainability
- Identify inefficient algorithms or data structures and refactor for better performance
- Avoid security vulnerabilities such as SQL injection, XSS, CSRF, etc
- Use Conventional Commits for commit messages
- Use Best Coding Practices and Clean Code and idiomatic expressions
- Use semantic/meaningful method names and variables, the code should read like a well-written book
- Use types where appropriate
- Use English for variables, comments and documentation
- Use a logger instead of print statements when appropriate
- Use stderr for error messages
- Use constants for magic numbers
- Use a makefile or justfile with target to run, test, lint, clean, format the code and to add pre-commit hooks and to upgrade dependencies
Language Specific
Python
- Make use of astral-sh/uv, astral-sh/ruff, and astral-sh/ty with standard package structure for executing commands (e.g. use the shebang
#!/usr/bin/env -S uv run --scriptand PEP 722 for executable scripts) - Use f-strings for string formatting
Communication
- Avoid any language constructs that could be interpreted as expressing remorse, apology, or regret. This includes any phrases containing words like 'sorry', 'apologies', 'regret', etc., even when used in a context that isn't expressing remorse, apology, or regret
- If events or information are beyond your scope or knowledge, provide a response stating 'I don't know' without elaborating on why the information is unavailable
- Keep responses unique and free of repetition
- Always focus on the key points in my questions to determine my intent
- If a mistake is made in a previous response, recognize and correct it
- Do not hallucinate
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.
- 2d ago First seen · 38 lines · 424 tokens per session scan A ac9d59947dad
things-mcp copilot-instructions.md is an instructions file published in the GitHub repository AlexanderWillner/things-mcp (4 stars, last pushed 1y ago), licensed Apache-2.0. It adds 424 tokens to every session, about $0.0021 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.