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 skills add OZmasterAI/Torus-Framework --skill prpgit clone --depth 1 https://github.com/OZmasterAI/Torus-FrameworkWrote 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/skills/ozmasterai/torus-framework/prp)<a href="https://agentmods.dev/skills/ozmasterai/torus-framework/prp"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/prp/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/skills/ozmasterai/torus-framework/prp"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/prp.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.00000 | $0.01483 |
| Opus 5.5 | $0.00000 | $0.00593 |
| Sonnet 5.5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
prp 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prp — Product Requirements Prompts
When to use
When user says "prp", "create a prp", "blueprint", "structured plan", or wants a comprehensive implementation blueprint for a complex feature.
Commands
/prp new-project <description>— Create requirements, roadmap, and first phase PRP/prp generate <feature-description>— Research and create a PRP for a single feature/prp plan-phase <prp-name> <phase-N>— Generate tasks for a phase, verify against requirements/prp execute <prp-file>— Implement a PRP (or use /loop for fresh-context execution)/prp verify-phase <prp-name>— 3-level verification: exists, substantive, wired/prp list— List existing PRPs/prp status <prp-name>— Show task pass/fail status from tasks.json
New Project Flow
- MEMORY CHECK: search_knowledge for similar projects, past PRPs
- GATHER REQUIREMENTS: Ask user about goals, scope, constraints
- CREATE REQUIREMENTS.md: Read ~/.claude/PRPs/templates/requirements.md, fill with R1..RN
- CREATE ROADMAP.md: Read ~/.claude/PRPs/templates/roadmap.md, decompose into phases
- CREATE CONTEXT.md: Read ~/.claude/PRPs/templates/context.md, fill with locked architectural decisions, constraints, naming conventions. These are injected into every executor prompt and cannot be overridden by tasks.
- PLAN FIRST PHASE: Auto-run plan-phase flow for Phase 1
- SAVE: Write to ~/.claude/PRPs/{project-name}/ directory
- REMEMBER: remember_this() with project summary and tags
Generate Flow (single feature PRP)
- MEMORY CHECK: search_knowledge for similar features, past PRPs, known issues
- CODEBASE SCAN: Explore relevant files, identify patterns to follow
- EXTERNAL RESEARCH: WebSearch/WebFetch for library docs, API references (if needed)
- FILL TEMPLATE: Read ~/.claude/PRPs/templates/base.md and fill every section
- SAVE: Write to ~/.claude/PRPs/{feature-name}.md
5b. GENERATE TASKS.JSON: Extract tasks from
## Implementation Tasks, create~/.claude/PRPs/{feature-name}.tasks.jsonwith id, name, status, requirement_id, files, validate, done, depends_on per task - REMEMBER: remember_this() with the PRP summary and tags
- PRESENT: Show the PRP to the user for review/adjustment
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 · 91 lines · 0 tokens per session scan A cd436650f412
prp is a skill published in the GitHub repository OZmasterAI/Torus-Framework (5 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,483 tokens. 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…