Borrowing it
Nothing to install: this file belongs to JetXu-LLM/DocMason. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JetXu-LLM/DocMason/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/JetXu-LLM/DocMasonWrote 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/jetxu-llm/docmason/copilot-instructions)<a href="https://agentmods.dev/instructions/jetxu-llm/docmason/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jetxu-llm/docmason/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/jetxu-llm/docmason/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jetxu-llm/docmason/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.00482 | $0.00482 |
| Opus 5.5 | $0.00193 | $0.00193 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
DocMason 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 1mo 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocMason GitHub Copilot Notes
Start by reading AGENTS.md.
AGENTS.md is the baseline repository contract.
This file is only the minimal GitHub Copilot adaptation layer for the current workspace.
For an ordinary user request in GitHub Copilot:
- after
AGENTS.md, the normal next read isskills/canonical/ask/SKILL.md - then open canonical
askthrough theCanonical Ask Contractin that skill and follow the returned route - do not start with
workspace-status,workspace-bootstrap, source search, CLI help, or ad hoc implementation reading unless the request is clearly explicit operator work or canonicalaskreturns that route - do not treat direct
retrieveortraceoutput as completion of the ask contract
For explicit operator work:
- follow the matching canonical workflow or stable
docmasonCLI fromAGENTS.md - do not force setup, status, sync, or review work through the ordinary ask front door
Copilot-Specific Delta
- Do not assume Codex-native behavior is available just because repository guidance mentions Codex as the native reference path.
- Use the current GitHub Copilot tool surface to achieve the same repository outcome when the exact Codex interaction model is different.
- If a Codex-oriented note assumes implicit image visibility, use explicit image inspection tools such as
view_image, or use published multimodal artifacts such asvisual_layoutand render-linked evidence instead of assuming that file paths are already visually available. - Treat differences in transcript fidelity, attachment capture, or image visibility as current adapter-surface differences unless the repository explicitly states a product limitation.
- If a Codex-oriented workflow mentions main and sub agents, keep the main agent responsible for critical-path reasoning, mutations, publication, and final sign-off. Use a subagent only when the current environment explicitly supports it and the delegated work is read-only or clearly disjoint.
- Prefer equivalent file reads, searches, validation surfaces, terminal commands, and published artifact inspection over inventing Copilot-only behavior.
- Do not assume Claude-specific helpers, generated skill shims, or interaction-history enrichments are loaded unless the current GitHub Copilot environment explicitly exposes them.
- Keep the adaptation minimal. Do not create a parallel GitHub Copilot product contract when the existing repository contract already applies.
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.
- 1mo ago First seen · 29 lines · 482 tokens per session scan A 14fb596c68b0
DocMason copilot-instructions.md is an instructions file published in the GitHub repository JetXu-LLM/DocMason (151 stars, last pushed 2d ago), licensed Apache-2.0. It adds 482 tokens to every session, about $0.0019 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.