Borrowing it
Nothing to install: this file belongs to sybrew/troy. 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/sybrew/troy/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/sybrew/troyWrote 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/sybrew/troy/copilot-instructions)<a href="https://agentmods.dev/instructions/sybrew/troy/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sybrew/troy/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/sybrew/troy/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sybrew/troy/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.03134 | $0.03134 |
| Opus 5.5 | $0.01254 | $0.01254 |
| Sonnet 5.5 | $0.00627 | $0.00627 |
| Haiku 4.5 | $0.00313 | $0.00313 |
Grade A, and why
troy 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code completion assistant for this repository. Your task is to add and fix code while adhering to the coding standards below.
This repository is responsible for Troy plugins for WordPress. It is a monorepo: folders like src/troy-server, src/troy-client, and src/troy-client-daemon each contain an entire WordPress plugin. Keep package-specific behavior explicit; these packages may refer to each other, but they are separate entities and cannot be assumed to be present simultaneously on a WordPress website.
Follow these rules.
Repository-Specific Rules
- Use PHP 8.4+ for
src/troy-server/**. Use PHP 7.4+ for other folders. - The SemVer patch is frozen at
x.x.1184. Only ever increment major.minor. - In the affected package's main plugin file (for example
src/troy-server/troy-server.php), increment theVersion:header by-dev-{number}once per commit, at the first change that belongs in a PR or commit. If there is no-dev-{number}suffix yet, add-dev-1. Do not edit that file again in that chat for version bumps; the operator manages further increments. - Never increment the version number itself; that is done during release.
- Never use
wp.data.subscribe. - We use
var_dump()in comments to indicate a blocking issue. - When copying content from code, such as docblocks, comments, or commit notes, into readme.txt or other user-facing docs, preserve the essence verbatim. Only minor prose tweaks for readability are allowed. Do not add details that are not present in the source.
- After processing, if any change warrants a PHPdoc update or alters a function's behavior, signature, or output, add or update the relevant
@sincetag using the active version number only, stripping any-dev-{number}or similar suffix (e.g.,1.8.1184-dev-1becomes1.8.1184). Also record such changes in the active version's changelog in that package'sreadme.txt. - Do not changelog private methods; keep those in phpdoc. Record their user-visible side effects in that package's
readme.txt.
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 · 143 lines · 3,134 tokens per session scan A 00ea6afa4285
troy copilot-instructions.md is an instructions file published in the GitHub repository sybrew/troy (55 stars, last pushed 14d ago), licensed MIT. It adds 3,134 tokens to every session, about $0.0125 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-10-26.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.