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 GlamgarOnDiscord/claude-saas-blueprint --skill prdgit clone --depth 1 https://github.com/GlamgarOnDiscord/claude-saas-blueprintWrote 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/glamgarondiscord/claude-saas-blueprint/prd)<a href="https://agentmods.dev/skills/glamgarondiscord/claude-saas-blueprint/prd"><img src="https://agentmods.dev/badge/skills/glamgarondiscord/claude-saas-blueprint/prd/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/glamgarondiscord/claude-saas-blueprint/prd"><img src="https://agentmods.dev/badge/skills/glamgarondiscord/claude-saas-blueprint/prd.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.00034 | $0.01056 |
| Opus 5 | $0.00017 | $0.00528 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00106 |
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 11d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modes
/prd brainstorm [idée] — Phase 1 : Exploration
Utiliser /brainstorm pour explorer l'idée :
- Quel problème ça résout ?
- Qui sont les utilisateurs cibles ?
- Quels sont les concurrents ?
- Quel est le business model ?
- Quel est le MVP minimal ?
Output : Synthèse validée par l'utilisateur.
/prd generate — Phase 2 : Rédiger le PRD
Générer un Product Requirements Document structuré dans docs/prd.md :
# PRD — [Nom du Produit]
## 1. Vision
- Problème résolu
- Proposition de valeur unique
- Utilisateurs cibles
## 2. Scope MVP
- Features incluses (must-have)
- Features exclues (v2, v3)
- Contraintes techniques
## 3. User Stories
- En tant que [rôle], je veux [action], afin de [bénéfice]
- Organisées par priorité (P0, P1, P2)
## 4. Architecture Technique
- Stack choisie (via /brainstorm si pas encore décidé)
- Schema de données (entités principales + relations)
- Diagramme de flux (auth, paiement, features core)
- Intégrations tierces (Stripe, email, etc.)
## 5. Pages & Navigation
- Sitemap avec toutes les pages
- Wireframes textuels des pages clés
## 6. API Endpoints
- Liste des endpoints nécessaires
- Formats de requête/réponse
## 7. Métriques de Succès
- KPIs à tracker
- Critères de "done" pour le MVP
/prd tasks — Phase 3 : Découper en Tasks
Transformer le PRD en tasks atomiques dans .claude/memory/roadmap/backlog.md :
Règles de découpage :
[S]= 1 fichier ou moins,[M]= 2-5 fichiers,[L]= 6+ fichiers (→ décomposer avant exec)- Chaque task = 1 commit logique, indépendante ou dépendances explicites
- Ordre : DB schema → Core logic → API → UI → Tests
- Grouper par sprint (Sprint 1 = fondations, Sprint 2 = features core, Sprint 3 = polish)
Format :
### Sprint 1 — Fondations
- [ ] [S] Setup projet avec /saas-init
- [ ] [M] Schema DB users + organizations + memberships
- [ ] [M] Auth flow (register, login, logout)
- [ ] [S] Layout principal (sidebar, header, navigation)
- [ ] [S] Page dashboard vide
### Sprint 2 — Core Features
- [ ] [M] Feature: [feature 1 du PRD]
- [ ] [M] Feature: [feature 2 du PRD]
- [ ] [M] Intégration Stripe (plans, checkout, webhooks)
### Sprint 3 — Polish & Ship
- [ ] [M] Landing page
- [ ] [S] SEO + meta tags
- [ ] [M] Tests E2E parcours critiques
- [ ] [S] Deploy check + mise en production
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.
- 11d ago First seen · 116 lines · 34 tokens per session scan A 580b805812d0
prd is a skill published in the GitHub repository GlamgarOnDiscord/claude-saas-blueprint (2 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,056 once invoked, about $0.0002 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 skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.