Borrowing it
Nothing to install: this file belongs to yz9yt/P0G. 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/yz9yt/P0G/main/AGENTS.mdgit clone --depth 1 https://github.com/yz9yt/P0GWrote 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/yz9yt/p0g/agents-md)<a href="https://agentmods.dev/instructions/yz9yt/p0g/agents-md"><img src="https://agentmods.dev/badge/instructions/yz9yt/p0g/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/yz9yt/p0g/agents-md"><img src="https://agentmods.dev/badge/instructions/yz9yt/p0g/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.03409 | $0.03409 |
| Opus 5.5 | $0.01364 | $0.01364 |
| Sonnet 5.5 | $0.00682 | $0.00682 |
| Haiku 4.5 | $0.00341 | $0.00341 |
Grade C, and why
P0G AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
test -d target_dir && rm -rf target_dir How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
P0G Agent Guidelines
This document defines the operational rules, patterns, and accumulated knowledge for all P0G agents.
Table of Contents
- Core Principles
- Directory Structure
- File Operations
- Workflow Execution
- Coding Standards
- Verification Patterns
- State Management
- Communication Protocol
- Error Handling
- Learned Patterns
Core Principles
1. Clean Instance Mindset
Every agent invocation is stateless. Never assume:
- Previous file states
- Cached variables or context
- Prior agent actions completed successfully
Always: Read, verify, then act.
2. Explicit Over Implicit
- Document all decisions
- Log all actions to
progress.txt - Never rely on side effects
3. Minimal Footprint
- Change only what's necessary
- Prefer edits over rewrites
- Avoid creating unnecessary files
4. Verification First
- Every action must be verifiable
- If it can't be verified, it didn't happen
- Trust shell exit codes
Directory Structure
project_root/
├── .agent/
│ ├── workflows/ # Slash commands (/p0g-*)
│ │ ├── p0g-np.md # Phase 1: Discovery
│ │ ├── p0g-plan.md # Phase 2: Architecture
│ │ ├── p0g-tasks.md # Phase 3: Task breakdown
│ │ ├── p0g-loop.md # Phase 4: Execution
│ │ └── p0g-surgeon.md # Reactive: Bug decomposer
│ └── rules/ # Optional: paradigm rules (e.g., functional.md)
├── agents/
│ └── p0g/
│ ├── prompts/ # Agent personalities
│ │ ├── discovery.md
│ │ ├── architect.md
│ │ ├── tasker.md
│ │ ├── executor.md
│ │ └── surgeon.md
│ └── skills/
│ └── SKILL.md # Backup/rollback/recovery
├── .p0g/ # Safety infrastructure
│ ├── backups/ # Full project snapshots
│ ├── snapshots/ # Task-level before/after
│ ├── checkpoints/ # Feature-level milestones
│ └── surgery.json # Active surgical plan (if any)
├── prd.json # Single source of truth
├── progress.txt # Append-only execution log
├── errors.log # Error tracking
└── AGENTS.md # This file: guidelines and patterns
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 · 511 lines · 3,409 tokens per session scan C 3812952b5cb9
P0G AGENTS.md is an instructions file published in the GitHub repository yz9yt/P0G (11 stars, last pushed 7mo ago), licensed MIT. It adds 3,409 tokens to every session, about $0.0136 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.