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/instructions/docs.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/docs)<a href="https://agentmods.dev/instructions/sybrew/troy/docs"><img src="https://agentmods.dev/badge/instructions/sybrew/troy/docs/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/docs"><img src="https://agentmods.dev/badge/instructions/sybrew/troy/docs.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.00428 | $0.00428 |
| Opus 5.5 | $0.00171 | $0.00171 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
troy docs.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
Documentation Rules
- Treat
readme.txtas a WordPress.org plugin readme using WordPress readme syntax, not generic plain text or GitHub Markdown. - Preserve the existing WordPress readme section markers and formatting conventions in
readme.txt. - Treat
readme.mdand similar repository documentation as product or package documentation, not as a WordPress.orgreadme.txt, unless the file being edited is explicitly a plugin readme. - Preserve the existing Markdown heading structure and formatting conventions in
readme.md. - Because Troy is a monorepo, keep the target package explicit in documentation. Do not blur Troy, Troy Server, Troy Client, Troy Client Daemon, and Troy Installer behavior together.
- When documenting commands, settings, endpoints, package names, or file paths, keep the exact names used in the codebase or UI.
- Treat
readme.txtchangelog entries as Troy package release notes. Preserve the existing house style: version headings (= x.x.1184 =) and simple past-tense bullets (Added,Fixed,Changed,Improved,Resolved,Removed). - Preserve the existing nested list and indentation style in
readme.txtchangelogs, including indented follow-up bullets where the current format uses them. - When copying content from code, such as docblocks, comments, or commit notes, into
readme.txt,readme.md, 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. - A symbol introduced in the unreleased version gets one changelog introduction. Do not add a later entry for edits made to it before release.
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 · 18 lines · 428 tokens per session scan A 5f4187a6bf3e
troy docs.instructions.md is an instructions file published in the GitHub repository sybrew/troy (55 stars, last pushed 14d ago), licensed MIT. It adds 428 tokens to every session, about $0.0017 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.