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.
git clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/prp-execute)<a href="https://agentmods.dev/commands/bravew/trove/prp-execute"><img src="https://agentmods.dev/badge/commands/bravew/trove/prp-execute/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/commands/bravew/trove/prp-execute"><img src="https://agentmods.dev/badge/commands/bravew/trove/prp-execute.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.00009 | $0.00709 |
| Opus 5.5 | $0.00004 | $0.00284 |
| Sonnet 5.5 | $0.00002 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
prp-execute 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute PRP
PRP File: $ARGUMENTS
Mission: One-Pass Implementation Success
PRPs enable working code on the first attempt through:
- Context Completeness: Everything needed, nothing guessed
- Progressive Validation: Multi-level gates catch errors early
- Pattern Consistency: Follow existing codebase approaches
Your Goal: Transform the PRP into working code that passes all validation gates.
Execution Process
1. Load PRP
- Read the specified PRP file completely
- Absorb all context, patterns, requirements
- Use the provided documentation references and file patterns
- Trust the PRP's strategic direction, but verify tactical details (imports, paths, names)
2. Pre-Implementation Check
- Verify all referenced files exist
- Check that patterns mentioned are accessible
- Detect project stack and confirm validation commands match
- Run any pre-requisite setup commands
3. Task-by-Task Implementation
For each task in the STEP-BY-STEP TASKS section:
a) Understand — Read task requirements and referenced patterns
b) Implement — Follow the specified pattern and project conventions:
- Check CLAUDE.md or project rules for naming conventions
- Apply the documented approach
- Handle edge cases mentioned
c) Validate immediately — Run the task's validation command
- If validation fails, fix and re-validate
- Don't proceed until current task passes
d) Mark complete — Update todo list to track progress
4. Full Validation
After all tasks complete, run every validation gate from the PRP:
Level 1: Lint/format
Level 2: Tests
Level 3: Build
Level 4: Manual validation (if specified)
Each level must pass before proceeding to the next.
5. Completion
- Work through the PRP's completion checklist
- Verify all acceptance criteria met
- Move completed PRP:
mv .claude/PRPs/{file}.md .claude/PRPs/completed/
Execution Rules
- Validation Gates: Each task must pass validation; iterate until passed
- Pattern Adherence: Follow existing patterns, don't create new ones
- No Shortcuts: Complete all validation steps
- If the PRP has errors: Fix the tactical details and note deviations in report
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.
- 1mo ago First seen · 114 lines · 9 tokens per session scan A e9adb624fb8a
prp-execute is a command published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 709 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.