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/suuus/ape-context/copilot-instructionsgit clone --depth 1 https://github.com/suuus/ape-contextWhat 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.01162 | $0.01162 |
| Opus 5 | $0.00581 | $0.00581 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
ape-context 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Enterprise Context
This project uses GitHub for source control, Jira for project management, Azure as the cloud platform, and Microsoft 365 (SharePoint, Teams, Outlook) for documentation and communication. CI/CD runs on GitHub Actions. Security scanning uses GitHub Advanced Security (Dependabot, CodeQL).
MCP Servers
GitHub (github-mcp-server) 🐙
- Covers: Repositories, pull requests, issues, code search, Actions workflows, security alerts
- Key tools:
github-mcp-server-search_code,github-mcp-server-list_issues,github-mcp-server-list_pull_requests,github-mcp-server-pull_request_read,github-mcp-server-actions_list,github-mcp-server-get_job_logs - When to use: For any GitHub operation — searching code, reading PRs, checking CI status, browsing issues. Prefer these tools over
ghCLI commands.
Jira (atlassian-jira) 👥
- Covers: Jira projects, issues, sprints, JQL search, dev info (commits, PRs linked to issues)
- When to use: When the user mentions Jira tickets, sprint planning, issue tracking, or project management. Use JQL for complex queries.
- Conventions: Always reference issues with the full project key (e.g.,
PROJ-123).
M365 Read — WorkIQ (workiq) 🐙
- Covers: SharePoint search, Outlook email queries, OneDrive files, Teams messages, Calendar — read-only
- Key tool:
workiq-ask_work_iq— ask natural-language questions about M365 data - When to use: When the user asks about emails, meetings, SharePoint documents, Teams messages, or calendar events. This is the primary tool for finding information across Microsoft 365.
M365 Write (microsoft-365) 👥
- Covers: SharePoint page creation/editing, sending emails, creating calendar events, managing files, contacts, groups
- When to use: When the user needs to create, edit, or send content in M365 (e.g., "create a SharePoint page", "send an email", "schedule a meeting"). For read/search operations, prefer
workiqinstead.
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 · 90 lines · 1,162 tokens per session scan A aa10bd7b003e
ape-context copilot-instructions.md is an instructions file published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,162 tokens to every session, about $0.0058 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
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.
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).
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.