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/pyk/cargo-txt/agents-mdgit clone --depth 1 https://github.com/pyk/cargo-txtWrote 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/pyk/cargo-txt/agents-md)<a href="https://agentmods.dev/instructions/pyk/cargo-txt/agents-md"><img src="https://agentmods.dev/badge/instructions/pyk/cargo-txt/agents-md.svg" alt="Measured on agentmods" 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 | $0.00548 | $0.00548 |
| Opus 5 | $0.00274 | $0.00274 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
cargo-txt 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 3d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tools
cargo-txt
Use cargo txt to access the crate documentation.
The workflow is:
- Build documentation:
cargo txt build <crate> - List all items:
cargo txt list <lib_name> - View specific item:
cargo txt show <lib_name>::<item>
For example:
# Build the serde crate documentation
cargo txt build serde
# List all items in serde
cargo txt list serde
# View serde crate overview
cargo txt show serde
# View serde::Deserialize trait documentation
cargo txt show serde::Deserialize
Guidelines
Instructions
Agent Modes
Planning Mode
When creating or updating a plan:
- Read README.md to understand the project.
- Use the guidelines.
- Use the thinking tool.
- Use
cargo-txtif needed. - Include README.md updates in the plan.
- IMPORTANT: Every plan's Success Criteria section MUST include these base
criteria:
rust-lintpassescargo clippy -- -D warningspassescargo buildsucceedscargo testpasses
- Read & follow Create Plan Instruction.
Building Mode
When implementing a plan:
- Update the plan status as in progress.
- Read README.md to understand the project.
- Use the guidelines.
- Use the
cargo-txttool. - Use the thinking tool.
- IMPORTANT: Do not use git restore commands (can cause data loss).
- IMPORTANT: Review and update the plan checklist after implementation.
Review Mode
When reviewing staged changes:
- Read README.md to understand the project.
- Use the guidelines.
- Use the thinking tool.
- Read & follow Review Changes Instruction.
- Use
cargo testto run tests andrust-lintto verify 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.
- 3d ago First seen · 89 lines · 548 tokens per session scan A 2dbd3ca06e6e
cargo-txt AGENTS.md is an instructions file published in the GitHub repository pyk/cargo-txt (11 stars, last pushed 3mo ago), licensed MIT. It adds 548 tokens to every session, about $0.0027 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.
Other instructions, from other repositories
VTCode copilot-instructions.md
Instructions for vinhnx/VTCode, covering vt code agent guidelines, build & test commands, preferred (faster with cargo-nextest), standard cargo commands and fallback (if nextest unavailable).
rust-lsp CLAUDE.md
Instructions for zircote/rust-lsp, covering claude.md, project overview, setup, key files and hook system.
rust-lsp copilot-instructions.md
Instructions for zircote/rust-lsp, covering copilot instructions, priorities, key files, commands and when adding hooks.
rust-doctor CLAUDE.md
Instructions for arthjean/rust-doctor, a project described as: Your agent writes bad Rust. This catches it.
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.