crates-docs AGENTS.md

Repository instructions for a Rust project, including its structure, build commands, and checks required before changes are merged.

In plain words
What is it for?
Building the project, checking formatting, running Clippy lint checks, and reviewing feature-gated code before a merge.
Why use it?
They give coding agents the project-specific rules needed to build and review changes consistently.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/kingingwang/crates-docs/agents-md
Clone the repo
git clone --depth 1 https://github.com/KingingWang/crates-docs

Made for: Codex, OpenCode.

Per session 2,240 This file is loaded in full into every session.
When invoked 2,240 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02240 $0.02240
Opus 5 $0.01120 $0.01120
Sonnet 5 $0.00448 $0.00448
Haiku 4.5 $0.00224 $0.00224

Measured 2d ago against content hash 38221f826789, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

crates-docs AGENTS.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.

AGENTS.md · 364 lines

How it starts

The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file provides comprehensive guidance to agents when working with code in this repository.

CI/CD Workflow & Code Gates

Project Structure

  • Rust Edition: 2021
  • Default Features: server, stdio, macros, cache-memory, logging, api-key
  • Optional Features: cache-redis, tls, auth, hyper-server, sse, streamable-http

Build Commands

# Standard build
cargo build

# Build with all features
cargo build --all-features

# Build with specific feature
cargo build --features cache-redis

# Release build
cargo build --release

Code Quality Gates (Must Pass Before Merge)

1. Formatting Check
cargo fmt -- --check
  • Checks if code is properly formatted
  • Use cargo fmt to auto-fix formatting issues
2. Clippy Linting
# Check without optional features
cargo clippy --all-targets -- -D warnings

# Check with all features (required - feature-gated code)
cargo clippy --all-features --all-targets -- -D warnings

Critical: Run both commands because Redis/auth code is feature-gated and checked separately.

  • -D warnings treats all warnings as errors
  • --all-targets includes lib, bins, tests, benches
3. Security Audit
cargo install cargo-audit
cargo audit

Testing Commands

Test Target Structure

Tests are split across THREE targets (not one suite):

# Unit tests (primary - new code goes here)
cargo test --test unit

# Legacy unit tests
cargo test --test unit_tests

# Integration tests
cargo test --test integration_tests

# E2E tests
cargo test --test e2e
Running Single Tests

Important: Use the correct target when running a single test:

# Correct: specify --test unit
cargo test --test unit test_oauth_config_github

# Correct: for tools_docs tests
cargo test --test unit test_lookup_crate_tool_execute_markdown

# Incorrect: will search all targets and may fail
cargo test test_oauth_config_github
Feature-Gated Testing
# Test with Redis cache (only when Redis is available)
cargo test --features cache-redis

# Test unit with Redis feature
cargo test --test unit --features cache-redis

# Test all features
cargo test --all-features

Read the full file on GitHub · 364 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. 2d ago First seen · 364 lines · 2,240 tokens per session scan A 38221f826789

Subscribe to this mod's changes

crates-docs AGENTS.md is an instructions file published in the GitHub repository KingingWang/crates-docs (13 stars, last pushed 29d ago), licensed MIT. It adds 2,240 tokens to every session, about $0.0112 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-30.