cargo-txt AGENTS.md

cargo-txt AGENTS.md is an instructions file for Codex, OpenCode from pyk/cargo-txt. It costs 548 tokens per session, scanned A, original, MIT.

Project instructions for using cargo-txt to read Rust crate documentation, with serde as the example. A Rust crate is a reusable package of Rust code.

In plain words
What is it for?
Use them when working on pyk/cargo-txt, documenting serde, planning changes, reviewing work, or checking Rust builds, linting, and tests.
Why use it?
They give an agent a defined way to build documentation, list library items, and inspect a crate or a specific item. They also set planning, review, coding, and validation requirements.

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/pyk/cargo-txt/agents-md
Clone the repo
git clone --depth 1 https://github.com/pyk/cargo-txt

Made for: Codex, OpenCode.

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 cargo-txt AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/pyk/cargo-txt/agents-md.svg)](https://agentmods.dev/instructions/pyk/cargo-txt/agents-md)
Your own site
<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>
Per session 548 This file is loaded in full into every session.
When invoked 548 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.00548 $0.00548
Opus 5 $0.00274 $0.00274
Sonnet 5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

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.

AGENTS.md · 89 lines

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:

  1. Build documentation: cargo txt build <crate>
  2. List all items: cargo txt list <lib_name>
  3. 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:

  1. Read README.md to understand the project.
  2. Use the guidelines.
  3. Use the thinking tool.
  4. Use cargo-txt if needed.
  5. Include README.md updates in the plan.
  6. IMPORTANT: Every plan's Success Criteria section MUST include these base criteria:
    • rust-lint passes
    • cargo clippy -- -D warnings passes
    • cargo build succeeds
    • cargo test passes
  7. Read & follow Create Plan Instruction.

Building Mode

When implementing a plan:

  1. Update the plan status as in progress.
  2. Read README.md to understand the project.
  3. Use the guidelines.
  4. Use the cargo-txt tool.
  5. Use the thinking tool.
  6. IMPORTANT: Do not use git restore commands (can cause data loss).
  7. IMPORTANT: Review and update the plan checklist after implementation.

Review Mode

When reviewing staged changes:

  1. Read README.md to understand the project.
  2. Use the guidelines.
  3. Use the thinking tool.
  4. Read & follow Review Changes Instruction.
  5. Use cargo test to run tests and rust-lint to verify changes.

Read the full file on GitHub · 89 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. 3d ago First seen · 89 lines · 548 tokens per session scan A 2dbd3ca06e6e

Subscribe to this mod's changes

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.