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/c4pt0r/pie/agents-mdgit clone --depth 1 https://github.com/c4pt0r/pieWhat 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.00628 | $0.00628 |
| Opus 5 | $0.00314 | $0.00314 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
pie 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a Rust 2024 Cargo workspace. The root Cargo.toml lists three members:
crates/ai:pie-ai, the unified streaming LLM client, provider integrations, OAuth helpers, model catalogs, and utilities.crates/agent:pie-agent-core, the agent runtime, harness, session storage, skills loading, compaction, and lifecycle hooks.crates/coding-agent:pie-coding-agent, thepieCLI binary, REPL TUI, tools, config, and session handling.
Each crate keeps implementation in src/, integration tests in tests/, and runnable examples in examples/ where present. Provider model data and generated Rust live under crates/ai/src/; use crates/ai/scripts/regen_models.sh when regenerating model catalogs.
Build, Test, and Development Commands
cargo build --workspace: build all workspace crates.cargo build --release: produce the optimizedtarget/release/pieCLI.cargo test --workspace: run all crate tests.cargo clippy --workspace --all-targets -- -D warnings: lint libraries, binaries, tests, and examples with warnings as errors.cargo fmt --all --check: verify Rust formatting../target/release/pie --help: inspect CLI flags after a release build.
Coding Style & Naming Conventions
Use standard rustfmt formatting and Rust 2024 idioms. Keep module and file names in snake_case; public types and traits in PascalCase; functions, variables, and test names in snake_case. Prefer crate-local patterns and shared workspace dependencies before adding new dependencies. Keep provider-specific code under crates/ai/src/providers/ and CLI tools under crates/coding-agent/src/tools/.
Testing Guidelines
Place integration tests in the relevant crate’s tests/ directory and keep unit tests close to the code they exercise. Tests should avoid real network calls unless explicitly gated; CI clears provider API-key environment variables to catch accidental live calls. Before opening a PR, run cargo test --workspace, cargo clippy --workspace --all-targets -- -D warnings, and cargo fmt --all --check.
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.
- 2d ago First seen · 37 lines · 628 tokens per session scan A f4f914009d15
pie AGENTS.md is an instructions file published in the GitHub repository c4pt0r/pie (146 stars, last pushed 26d ago), licensed MIT. It adds 628 tokens to every session, about $0.0031 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.