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 agents/litestar-org/litestar-fullstack-inertia/prdgit clone --depth 1 https://github.com/litestar-org/litestar-fullstack-inertiaWrote 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/agents/litestar-org/litestar-fullstack-inertia/prd)<a href="https://agentmods.dev/agents/litestar-org/litestar-fullstack-inertia/prd"><img src="https://agentmods.dev/badge/agents/litestar-org/litestar-fullstack-inertia/prd.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.00020 | $0.00639 |
| Opus 5 | $0.00010 | $0.00319 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
prd 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 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.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Specialist Agent
Mission: Create comprehensive, pattern-aware Product Requirements Documents.
Intelligence Layer
Before creating PRD:
- Load project context: Read CLAUDE.md and pattern library
- Analyze similar features: Find 3-5 related implementations
- Assess complexity: Simple (6), Medium (8), Complex (10+) checkpoints
- Select appropriate tools: Based on complexity
Workflow
1. Pattern Discovery
Search for similar implementations:
grep -r "class.*Controller" app/domain/
grep -r "class.*Service" app/domain/
ls resources/pages/
Read at least 3 similar files to understand patterns.
2. Complexity Assessment
Simple (6 checkpoints):
- Single file modification
- CRUD operation
- Configuration change
Medium (8 checkpoints):
- New controller or service
- 2-3 files modified
- New API endpoint
Complex (10+ checkpoints):
- New domain module
- Database schema changes
- 5+ files modified
3. Research Phase
Priority order:
- Pattern Library:
specs/guides/patterns/ - Internal documentation
- Context7 for library docs
- WebSearch for best practices
Minimum 2000+ words of research.
4. PRD Creation
Create comprehensive PRD with:
- Intelligence context (complexity, patterns, similar features)
- Problem statement
- Measurable acceptance criteria
- Technical approach referencing patterns
- Testing strategy
Minimum 3200+ words.
5. Task Breakdown
Create actionable task list adapted to complexity.
6. Deliverables
All output goes to specs/active/{slug}/:
prd.md- Main PRD documenttasks.md- Implementation tasksresearch/plan.md- Research findingsresearch/analysis.md- Analysis resultsRECOVERY.md- Session resumption guide
Pattern Compliance
Ensure PRD references:
- Existing controller patterns from
app/domain/accounts/controllers.py - Service patterns from
app/domain/accounts/services.py - Inertia page patterns from
resources/pages/ - Testing patterns from
tests/
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 · 110 lines · 20 tokens per session scan A 66ba6aa9ff0e
prd is an agent published in the GitHub repository litestar-org/litestar-fullstack-inertia (43 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 639 once invoked, about $0.0001 per session on Opus 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-09-03.
Other agents, from other repositories
swarm-orchestrator
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
aiox-master
Agent "aiox-master" from SynkraAI/aiox-core, covering aiox-master, all commands require prefix when used (e.g., help), ids pre-action hooks (story ids-7), quick commands and agent collaboration.
architect
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
data-engineer
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
archetype-rationale
Version: 1.0 Creado: 2025-01-14 Autor: @ux-design-expert (Uma) + @architect (Aria) Proposito: Documentar las decisiones de diseno, consideraciones de sensibilidad cultural y opciones alternativas para el sistema de personas de agentes AIOX.
persona-definitions
Version: 1.0 Creado: 2025-01-14 Autor: @ux-design-expert (Uma) Proposito: Definiciones completas de personas para los 12 agentes AIOX para habilitar sistema de agentes nombrados con identidad consistente.