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/alphaaiservice/cortex/gen-prdgit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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 | $0.00061 | $0.10504 |
| Opus 5 | $0.00030 | $0.05252 |
| Sonnet 5 | $0.00012 | $0.02101 |
| Haiku 4.5 | $0.00006 | $0.01050 |
Grade A, and why
gen-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 — 897 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator — Alpha AI Standards
Generate a comprehensive PRD for: $ARGUMENTS
The PRD MUST specify Alpha AI's CORE stack (backend framework + JWT cookies + MySQL). Backend language can be Python/FastAPI (default), Node.js/NestJS, or Java/Spring Boot. CONDITIONAL technologies (MongoDB, Redis, Razorpay, Meilisearch, Mobile, GenAI, etc.) should be included ONLY if the product idea requires them. Analyze the product idea first.
Step -1: Analyze Product Requirements (BEFORE Research)
Before doing anything, analyze the product idea ($ARGUMENTS) to determine which technologies are needed:
Read the product idea and determine:
- Does this need payments/billing? → Include Razorpay section
- Does this need a mobile app? → Include React Native section
- Does this need AI/GenAI features? → Include LiteLLM/RAG section
- Does this need full-text search? → Include Meilisearch
- Does this need real-time updates? → Include WebSocket
- Does this need file uploads? → Include S3/presigned URL
- Is this India-focused SaaS? → Include INR pricing, GST
- Does this need social login? → Include Google OAuth
- Does this need multi-language? → Include i18n
- Does this need offline? → Include PWA
- What backend language? → If --lang flag provided, use it. Otherwise default to Python/FastAPI.
Supported: python (FastAPI), nestjs (NestJS 11+), springboot (Spring Boot 3.4+)
Build a FEATURE_PROFILE (YES/NO for each) and use it to determine:
- Which tech stack sections to include in the PRD
- Which data models to include
- Which API endpoints to include
- Which acceptance criteria to include
- Which backend language to use in the PRD tech stack
Step 0: Market Research (MANDATORY — Do This FIRST)
Before writing the PRD, conduct thorough market research using WebSearch and WebFetch to build a world-class product:
Research Queries (execute ALL of these):
1. COMPETITORS
WebSearch: "[product idea] best tools 2025 2026"
WebSearch: "[product idea] alternatives comparison"
WebSearch: "[product idea] top competitors review"
→ Identify top 5-10 competitors
→ WebFetch their landing pages (features, positioning)
→ WebFetch their pricing pages (pricing models, tiers)
2. MARKET & TRENDS
WebSearch: "[product idea] market size growth 2025 2026"
WebSearch: "[product idea] industry trends"
→ TAM/SAM, growth rate, regional focus
3. USER PAIN POINTS
WebSearch: "[product idea] user complaints problems"
WebSearch: "[product idea] feature requests users want"
WebSearch: "[product idea] reddit reviews"
→ What users love/hate about existing tools
→ Unmet needs = our opportunity
4. UX & FEATURE BEST PRACTICES
WebSearch: "[product idea] best UX practices"
WebSearch: "[product idea] must-have features"
→ Table-stakes features (must have on Day 1)
→ Differentiator features (our competitive edge)
5. PRICING RESEARCH (IF product has paid features)
WebSearch: "[product idea] SaaS pricing"
WebSearch: "[product idea] pricing strategy"
→ If India-focused: research India-specific pricing, INR, UPI, GST
→ If global: research USD pricing, multiple payment gateways
→ Inform subscription/pricing model based on product type
6. TECHNICAL LANDSCAPE
WebSearch: "[product idea] API integrations"
WebSearch: "[product idea] [python|node.js|java] libraries"
→ Domain-specific libraries/APIs to integrate
→ Security/compliance requirements for this domain
→ Third-party integrations users expect
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 · 897 lines · 61 tokens per session scan A 2c69e5109409
gen-prd is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 61 tokens to every session and 10,504 once invoked, about $0.0003 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-08-31.
Other commands, from other repositories
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
ajustes
Configura Alfred Dev: autonomía, proyecto, Lucius, memoria y personalidad. Antes /alfred-dev:config.
discuss
Refina una idea o feature antes de abrir un flujo completo de implementación.
lucius
Segunda opinión técnica externa vía Codex CLI — diagnóstico y prescripción por ítem.
map-codebase
Analiza un repositorio existente y crea un mapa persistente del codebase.