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/antiotaku/github-copilot-instructions/markdowngit clone --depth 1 https://github.com/antiotaku/github-copilot-instructionsWhat 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.00749 | $0.00749 |
| Opus 5 | $0.00375 | $0.00375 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
github-copilot-instructions markdown.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 yesterday.
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.
This is a copy
94% identical to ssd-ai markdown.instructions.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Content Rules
The following markdown content rules are enforced in the validators:
- Headings: Use appropriate heading levels (H2, H3, etc.) to structure your content. Do not use an H1 heading, as this will be generated based on the title.
- Lists: Use bullet points or numbered lists for lists. Ensure proper indentation and spacing.
- Code Blocks: Use fenced code blocks for code snippets. Specify the language for syntax highlighting.
- Links: Use proper markdown syntax for links. Ensure that links are valid and accessible.
- Images: Use proper markdown syntax for images. Include alt text for accessibility.
- Tables: Use markdown tables for tabular data. Ensure proper formatting and alignment.
- Line Length: Limit line length to 400 characters for readability.
- Whitespace: Use appropriate whitespace to separate sections and improve readability.
- Front Matter: Include YAML front matter at the beginning of the file with required metadata fields.
Formatting and Structure
Follow these guidelines for formatting and structuring your markdown content:
- Headings: Use
##for H2 and###for H3. Ensure that headings are used in a hierarchical manner. Recommend restructuring if content includes H4, and more strongly recommend for H5. - Lists: Use
-for bullet points and1.for numbered lists. Indent nested lists with two spaces. - Code Blocks: Use triple backticks (
) to create fenced code blocks. Specify the language after the opening backticks for syntax highlighting (e.g.,csharp). Use escaped form\\ninstead of\nwhen documenting escape sequences to prevent markdown rendering issues. - Links: Use
[link text](URL)for links. Ensure that the link text is descriptive and the URL is valid. - Images: Use
for images. Include a brief description of the image in the alt text. - Tables: Use
|to create tables. Ensure that columns are properly aligned and headers are included. - Line Length: Break lines at 80 characters to improve readability. Use soft line breaks for long paragraphs.
- Whitespace: Use blank lines to separate sections and improve readability. Avoid excessive whitespace.
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.
- yesterday First seen · 53 lines · 749 tokens per session scan A 55198d3f5902
github-copilot-instructions markdown.instructions.md is an instructions file published in the GitHub repository antiotaku/github-copilot-instructions (1 stars, last pushed 10mo ago), licensed MIT. It adds 749 tokens to every session, about $0.0037 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to ssd-ai markdown.instructions.md, differing in 2 lines, and is treated as a copy.
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.
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.
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).
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.