copilot-instructions: Instructions file for GitHub Copilot

.github/instructions/rust-testing.instructions.md

copilot-instructions rust-testing.instructions.md is an instructions file for GitHub Copilot from ThiagoGuislotti/copilot-instructions. It costs 3,004 tokens per session, scanned A, original, MIT.

Testing rules for Rust projects, including required test files, naming, documentation, and coverage of public APIs. Rust is a programming language, and a crate is one Rust package or library.

In plain words
What is it for?
Use them to organize tests around a required test_suite.rs entry point, add error and integration tests, name tests clearly, and document each test file.
Why use it?
They give every crate a predictable test layout, making tests easier to find, run, and maintain as the code grows.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is ThiagoGuislotti/copilot-instructions's own configuration. It tells GitHub Copilot how to work on copilot-instructions itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything copilot-instructions configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ThiagoGuislotti/copilot-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ThiagoGuislotti/copilot-instructions/main/.github/instructions/rust-testing.instructions.md
Clone the repo
git clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructions

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for copilot-instructions rust-testing.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/rust-testing/github.svg)](https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/rust-testing)
Your own site
<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/rust-testing"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/rust-testing/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.

agentmods 80×15 button for copilot-instructions rust-testing.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/rust-testing"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/rust-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,004 This file is loaded in full into every session.
When invoked 3,004 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03004 $0.03004
Opus 5.5 $0.01202 $0.01202
Sonnet 5.5 $0.00601 $0.00601
Haiku 4.5 $0.00300 $0.00300

Measured 1mo ago against content hash 8976292d3dbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.github/instructions/rust-testing.instructions.md · 489 lines

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

  1. Test Coverage: Every public API must have tests
  2. Test Organization: Use dedicated test files, not just inline tests
  3. Test Naming: Descriptive names following test_[function]_[scenario]_[result] pattern
  4. Documentation: All test files must have file-level doc comments
  5. Template Precedence: Start concrete test files from the applicable .github/templates/rust-*-template.rs file 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:

  1. ✅ ALWAYS use test_suite.rs as the entry point
  2. ✅ Import all test modules in test_suite.rs
  3. ✅ Mirror src/ structure in tests/
  4. ✅ Use #[path] for subdirectories
  5. ❌ NEVER use lib.rs in tests/
  6. ❌ NEVER use individual test files without test_suite.rs
  7. ❌ 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)

Read the full file on GitHub · 489 lines

Changes

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.

  1. 1mo ago First seen · 489 lines · 3,004 tokens per session scan A 8976292d3dbb

Subscribe to this mod's changes

copilot-instructions rust-testing.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 3mo ago), licensed MIT. It adds 3,004 tokens to every session, about $0.0120 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.

Related

Other instructions, from other repositories

flow-like copilot-instructions.md

Copilot instructions for Rheosoph/flow-like, covering flow-like wasm node development — rust, project overview, build & test, architecture and pin types.

Rheosoph/flow-like · 1,349 tokens

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens