Borrowing it
Nothing to install: this file belongs to dineshdb/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.
curl -O https://raw.githubusercontent.com/dineshdb/pie/main/AGENTS.mdgit clone --depth 1 https://github.com/dineshdb/pieWrote 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/dineshdb/pie/agents-md)<a href="https://agentmods.dev/instructions/dineshdb/pie/agents-md"><img src="https://agentmods.dev/badge/instructions/dineshdb/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.
<a href="https://agentmods.dev/instructions/dineshdb/pie/agents-md"><img src="https://agentmods.dev/badge/instructions/dineshdb/pie/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.00539 | $0.00539 |
| Opus 5.5 | $0.00216 | $0.00216 |
| Sonnet 5.5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
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 26d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When it seems like I'm talking about or giving instructions to claude, I'm actually talking about this ai agent I'm building: pie. Work on local context. Don't assume and rewrite the global prompt. I'm talking about this project.
Testing
After each change, run following tests to verify if the change is valid.
- repo test
- test.py gives a summary of issues in the codebase based on runtime behavior. You should review the response and try to fix the issues.
- Deterministic tests go to the rust tests, non deterministic tests go to tests.yaml.
- You are not allowed to change tests just to make tests pass
- Tests should check the behavior of the program (specs) instead of implementation details
Architecture
- You should always rethink the available codebase in terms of new feature being added. Identify how it diverges, identifying places to trim, changes in architecture and organization to slim down and /simplify the codebase to keep it lean and clean.
- Prefer newtypes over raw types
- Use turso (the in-process SQLite-compatible engine) for persistence —
never sqlx or another SQL driver. Statically typed queries, one store
(
pie-acp'sstore,~/.pie/pie.db), idempotent baseline schema — no migration runner. - pie-tui is stateless: it owns no database and persists nothing. The
store belongs to
pie acp. - One binary:
pie. No alias binaries.
I'm an Idiot
So make the codebase foolproof. Add tests, lints, automatic formatting, git hooks(suggest some), etc. You have a memory of a goldfish so you don't remember, I'm a fool. So write those instructions and rules somewhere for reusability. Don't make me angry because I get easily angry just like Hulk. I'm always angry.
Simplification
- follow rust 2024 ergonomics
- use early return patterns and other patterns for simpler logic
- try to use dry principle but not always.
- use From impl instead of from_ to_ methods.
- Try to reduce copies for simple steps, use &'str and other references. However, don't complicate structs with references. Instead, opt to rearchitect the problem in a way copies are unnecessary. Hexagonal architecture, MVU patterns, etc help with this.
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.
- 26d ago Changed · +6 lines · +86 tokens per session 230e5250b562
- 1mo ago First seen · 46 lines · 453 tokens per session scan A 9ea2d56a65d9
pie AGENTS.md is an instructions file published in the GitHub repository dineshdb/pie (2 stars, last pushed 27d ago), licensed MIT. It adds 539 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-31.
Other instructions, from other repositories
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).