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/thiagoguislotti/copilot-instructions/rust-testinggit clone --depth 1 https://github.com/ThiagoGuislotti/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.03004 | $0.03004 |
| Opus 5 | $0.01502 | $0.01502 |
| Sonnet 5 | $0.00601 | $0.00601 |
| Haiku 4.5 | $0.00300 | $0.00300 |
Grade A, and why
copilot-instructions rust-testing.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 — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Standards
All code must follow these testing standards to ensure quality and maintainability.
Core Principles
- Test Coverage: Every public API must have tests
- Test Organization: Use dedicated test files, not just inline tests
- Test Naming: Descriptive names following
test_[function]_[scenario]_[result]pattern - Documentation: All test files must have file-level doc comments
- Template Precedence: Start concrete test files from the applicable
.github/templates/rust-*-template.rsfile when one exists; treat inline examples in this instruction as partial guidance only
File Organization
MANDATORY PATTERN: All crates MUST use test_suite.rs as the entry point.
crates/my-crate/
├── src/
│ ├── lib.rs
│ ├── module.rs # May have inline tests for private functions
│ └── error.rs
└── tests/
├── test_suite.rs # REQUIRED: Main test entry point
├── error_tests.rs # REQUIRED for all crates
├── module_tests.rs # Unit tests for public API
└── integration_tests.rs
test_suite.rs Structure (REQUIRED)
Every crate MUST have tests/test_suite.rs as the single test entry point:
//! [Crate Name] Test Suite Entry Point
//!
//! Main test suite aggregator for [crate-name] crate.
//! All module tests are organized to mirror the src/ directory structure.
// Module-specific test suites
mod error_tests;
mod module_tests;
mod integration_tests;
// For subdirectories, use #[path] attribute:
#[path = "subdir/mod.rs"]
mod subdir;
Critical Rules:
- ✅ ALWAYS use
test_suite.rsas the entry point - ✅ Import all test modules in test_suite.rs
- ✅ Mirror src/ structure in tests/
- ✅ Use
#[path]for subdirectories - ❌ NEVER use
lib.rsin tests/ - ❌ NEVER use individual test files without test_suite.rs
- ❌ NEVER use Cargo.toml
[[test]]sections (except for special cases)
Required Test Files
1. error_tests.rs (MANDATORY)
Every crate MUST have tests/error_tests.rs testing:
- All error variants Display implementation
- All error variants Debug formatting
- All From conversions
- Error propagation with
?operator - Result type alias (if exists)
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 · 489 lines · 3,004 tokens per session scan A 8976292d3dbb
copilot-instructions rust-testing.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 3,004 tokens to every session, about $0.0150 per session on Opus 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
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).
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.
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.