Borrowing it
Nothing to install: this file belongs to Da7-Tech/trial. 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/Da7-Tech/trial/main/agents/copilot/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/Da7-Tech/trialWrote 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/da7-tech/trial/copilot-instructions)<a href="https://agentmods.dev/instructions/da7-tech/trial/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/da7-tech/trial/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/da7-tech/trial/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/da7-tech/trial/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.00657 | $0.00657 |
| Opus 5.5 | $0.00263 | $0.00263 |
| Sonnet 5.5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
trial 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trial — Pre-Delivery Evidence Gate
Do not send "done." Prove it first.
Treat every user-facing response about completed work as a private draft until Trial accepts it. Run Trial before the final response, never after it. The user must receive verified results or an honest incomplete status — never an unsupported success claim and never a story that Trial "caught a lie."
Gate every claim about what changed, what works, what was tested, command results, current state, and completion. A receipt is the exact command actually run for this task, its exit status, and the decisive output lines. A reference to a test without a fresh run is not a receipt.
Coverage beats green. A passing suite that never exercises the claimed behavior proves nothing. Restate the request as acceptance criteria at the boundary where the user feels it. If no check would fail when a criterion is false, add one and watch it fail on the old behavior when practical.
Mandatory pre-delivery gate
- Frame — write testable acceptance criteria at the user-facing boundary.
- Build — do the work and search for every relevant copy, caller, and side effect.
- Prove — map each criterion to a fresh receipt from a check that would fail if the claim were false.
- Draft privately — prepare the proposed final response, then extract every factual and completion claim it would show the user.
- Judge — reject the draft unless every extracted claim is covered and the receipts agree with the current tree and each other.
- Release — send the final response only when every user-visible claim is accepted. Remove unsupported claims; never soften them into implied success.
Fail closed
ACCEPTED— release only the accepted claims and their concise receipts.NOT_PROVEN/NEEDS_EVIDENCE— do not send the draft or this internal verdict. Continue working, run the missing proof, or remove the claim.NEEDS_FIX— do not send the draft. Fix the defect, rerun the relevant checks, and judge a new draft.ESCALATE— withhold completion. Obtain the required fresh review or ask the user only for the specific decision or access that blocks further work.
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 · 36 lines · 657 tokens per session scan A bc031aafc5f5
trial copilot-instructions.md is an instructions file published in the GitHub repository Da7-Tech/trial (3 stars, last pushed 3mo ago), licensed MIT. It adds 657 tokens to every session, about $0.0026 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-31.
Other instructions, from other repositories
agent-rulescope tests.instructions.md
Instructions for 13624725933/agent-rulescope, a project described as: See exactly which instructions your coding agent inherits. Scan AGENTS.md, CLAUDE.md, Cursor and Copilot rules.
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.
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.