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/kandil7/prprompts-flutter-generator/creategit clone --depth 1 https://github.com/Kandil7/prprompts-flutter-generatorWrote 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/kandil7/prprompts-flutter-generator/create)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/create"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/create.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 | $0.00013 | $0.02369 |
| Opus 5 | $0.00006 | $0.01184 |
| Sonnet 5 | $0.00003 | $0.00474 |
| Haiku 4.5 | $0.00001 | $0.00237 |
Grade A, and why
Generate 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 4d 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Product Requirements Document
Overview
Generate a comprehensive Product Requirements Document (PRD) for a Flutter application. The PRD includes structured YAML frontmatter followed by detailed product specifications.
Instructions
Step 0: Template Selection (NEW in v4.1)
FIRST, ask the user if they want to start from an industry template:
🚀 PRD Generation - Starting Point
Would you like to start from an industry template? Templates include pre-configured compliance,
features, and best practices for specific domains.
Available templates:
1. Healthcare - HIPAA-compliant, PHI encryption, patient portal features
2. Fintech - PCI-DSS compliant, payment security, never store card numbers
3. Education - COPPA/FERPA compliant, parental consent, student data protection
4. E-commerce - PCI-DSS + Stripe, shopping cart, product catalog, secure checkout
5. Logistics - GPS tracking, route optimization, offline-first, proof of delivery
6. SaaS/B2B - Multi-tenancy, enterprise SSO, subscription billing, audit logs
7. Generic - Start from scratch, fully customized
Selection (1-7):
IF user selects 1-6: Load the corresponding template from templates/prd-{type}-starter.md:
prd-healthcare-starter.md(1)prd-fintech-starter.md(2)prd-education-starter.md(3)prd-ecommerce-starter.md(4)prd-logistics-starter.md(5)prd-saas-starter.md(6)
Template Loading Process:
- Read the selected template file
- Parse its YAML frontmatter (extract all key-value pairs)
- Use template values as defaults for Step 1 questions
- Display:
✅ Loaded [Type] template with pre-configured [compliance list] - Proceed to Step 1 with defaults populated
IF user selects 7 (Generic): Proceed to Step 1 with no defaults.
Template Customization: After loading a template, user can still customize:
- Project name (always required)
- Add/remove features
- Adjust team composition
- Modify timelines
- Add additional compliance requirements
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.
- 4d ago First seen · 323 lines · 13 tokens per session scan A 7950f41e5e51
Generate PRD is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 2,369 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-08-30.
Other commands, from other repositories
speckit.bug.fetch
Load an existing GitHub issue into the bug workflow (the complement of bug.issue) and seed a triage draft.
speckit.chore.fetch
Load an existing GitHub issue into the chore workflow and seed a triage draft.
speckit.chore.implement
Implement the scoped chore (the actual maintenance work) and record what changed.
speckit.gh-triage.feature
Create a GitHub issue describing a new feature, label it with the configured feature label, and optionally auto-run speckit.specify to turn it into a spec.
speckit.bug.pr
Open a pull request for the applied bug fix, linking the tracked issue.
create-prd
Generate a comprehensive Product Requirements Document (PRD) from conversation context.