Borrowing it
Nothing to install: this file belongs to pyk/cargo-txt. 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/pyk/cargo-txt/main/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/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/pyk/cargo-txt/agents-md"><img src="https://agentmods.dev/badge/instructions/pyk/cargo-txt/agents-md.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.00548 | $0.00548 |
| Opus 5.5 | $0.00219 | $0.00219 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (10 stars, last pushed 5mo ago), licensed MIT. It adds 548 tokens to every session, about $0.0022 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-30.
cargo-txt AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cargo-txt AGENTS.mdpyk/cargo-txt | Instructions file | 10 | 5mo ago | MIT | A | 548 | Codex, OpenCode |
| flow-like copilot-instructions.mdRheosoph/flow-like | Instructions file | 972 | yesterday | none | A | 1,349 | GitHub Copilot |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | yesterday | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |