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 commands/mturac/everything-openai-codex/prp-implementgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/commands/mturac/everything-openai-codex/prp-implement)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/prp-implement"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/prp-implement.svg" alt="Measured on agentmods" 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.00008 | $0.02369 |
| Opus 5 | $0.00004 | $0.01184 |
| Sonnet 5 | $0.00002 | $0.00474 |
| Haiku 4.5 | $0.00001 | $0.00237 |
Grade A, and why
prp-implement scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
if curl -sf http://localhost:PORT/health >/dev/null 2>&1; then Copies of this mod
1 near-identical copy found in the catalogue:
- prp-implement — 97% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapted from PRPs-agentic-eng by Wirasm. Part of the PRP workflow series.
PRP Implement
Execute a plan file step-by-step with continuous validation. Every change is verified immediately — never accumulate broken state.
Core Philosophy: Validation loops catch mistakes early. Run checks after every change. Fix issues immediately.
Golden Rule: If a validation fails, fix it before moving on. Never accumulate broken state.
Phase 0 — DETECT
Package Manager Detection
| File Exists | Package Manager | Runner |
|---|---|---|
bun.lockb |
bun | bun run |
pnpm-lock.yaml |
pnpm | pnpm run |
yarn.lock |
yarn | yarn |
package-lock.json |
npm | npm run |
pyproject.toml or requirements.txt |
uv / pip | uv run or python -m |
Cargo.toml |
cargo | cargo |
go.mod |
go | go |
Validation Scripts
Check package.json (or equivalent) for available scripts:
# For Node.js projects
cat package.json | grep -A 20 '"scripts"'
Note available commands for: type-check, lint, test, build.
Phase 1 — LOAD
Read the plan file:
cat "$ARGUMENTS"
Extract these sections from the plan:
- Summary — What is being built
- Patterns to Mirror — Code conventions to follow
- Files to Change — What to create or modify
- Step-by-Step Tasks — Implementation sequence
- Validation Commands — How to verify correctness
- Acceptance Criteria — Definition of done
If the file doesn't exist or isn't a valid plan:
Error: Plan file not found or invalid.
Run /prp-plan <feature-description> to create a plan first.
CHECKPOINT: Plan loaded. All sections identified. Tasks extracted.
Phase 2 — PREPARE
Git State
git branch --show-current
git status --porcelain
Branch Decision
| Current State | Action |
|---|---|
| On feature branch | Use current branch |
| On main, clean working tree | Create feature branch: git checkout -b feat/{plan-name} |
| On main, dirty working tree | STOP — Ask user to stash or commit first |
| In a git worktree for this feature | Use the worktree |
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 · 386 lines · 8 tokens per session scan A b39186e99ac0
prp-implement is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 12d ago), licensed MIT. It adds 8 tokens to every session and 2,369 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
update-faq
could you please update DESIGNFAQ & DXFAQ based on the changes we are trying to achieve.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
verify
Spawn a fresh-context verifier subagent to check completed work against its specification before trusting it.
weave
Improve active harnesses based on real use, failures, and corrections.