agentmods.dev

pie: Instructions file for Codex

AGENTS.md

pie AGENTS.md is an instructions file for Codex, OpenCode from c4pt0r/pie. It costs 628 tokens per session, scanned A, original, MIT.

Repository instructions for a Rust project: its folder structure, build and test commands, code style, and testing rules.

In plain words
What is it for?
Use them when building, testing, formatting, linting, or navigating the project's Rust workspace.
Why use it?
They give a coding agent the project-specific rules it needs before changing or checking the code.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is c4pt0r/pie's own configuration. It tells Codex and OpenCode how to work on pie itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pie configures →

not rated 173repo +3 3mo ago A scan 628 tokens original MIT
View source ↗ c4pt0r/pie
Reuse

Borrowing it

Nothing to install: this file belongs to c4pt0r/pie. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/c4pt0r/pie/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/c4pt0r/pie

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 pie AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/c4pt0r/pie/agents-md/github.svg)](https://agentmods.dev/instructions/c4pt0r/pie/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/c4pt0r/pie/agents-md"><img src="https://agentmods.dev/badge/instructions/c4pt0r/pie/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.

agentmods 80×15 button for pie AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/c4pt0r/pie/agents-md"><img src="https://agentmods.dev/badge/instructions/c4pt0r/pie/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 628 This file is loaded in full into every session.
When invoked 628 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00628 $0.00628
Opus 5.5 $0.00251 $0.00251
Sonnet 5.5 $0.00126 $0.00126
Haiku 4.5 $0.00063 $0.00063

Measured 2mo ago against content hash f4f914009d15, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

AGENTS.md · 37 lines

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, the pie CLI 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 optimized target/release/pie CLI.
  • 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.

Read the full file on GitHub · 37 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. 2mo ago First seen · 37 lines · 628 tokens per session scan A f4f914009d15

Subscribe to this mod's changes

pie AGENTS.md is an instructions file published in the GitHub repository c4pt0r/pie (173 stars, last pushed 3mo ago), licensed MIT. It adds 628 tokens to every session, about $0.0025 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.

Related

pie AGENTS.md compared with instructions from other repositories

pie AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pie AGENTS.mdc4pt0r/pieInstructions file1733mo agoMITA628Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode