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/validate-fluttergit 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/validate-flutter)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/validate-flutter"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/validate-flutter.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.00000 | $0.02250 |
| Opus 5 | $0.00000 | $0.01125 |
| Sonnet 5 | $0.00000 | $0.00450 |
| Haiku 4.5 | $0.00000 | $0.00225 |
Grade A, and why
validate-flutter 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Flutter Code
You are validating Flutter code quality, security, performance, and compliance using the PRPROMPTS validation system.
Overview
This command runs comprehensive validation checks on Flutter code and generates detailed reports with actionable recommendations.
Steps
1. Gather Information
Ask the user:
-
Flutter project path: Where is the Flutter project?
- Example:
./flutter-app,.,./mobile - Validate that pubspec.yaml exists
- Example:
-
Validation strictness: What level of strictness?
- Strict: High standards (min score 85/100)
- Standard: Balanced (min score 70/100) - recommended
- Lenient: Permissive (min score 50/100)
- Security: Focus on security issues only
- Performance: Focus on performance issues only
-
Report format: How should results be displayed?
- Terminal: Colorized output in terminal (default)
- HTML: Interactive HTML report with charts
- JSON: Machine-readable format
- Markdown: Documentation-friendly format
-
Auto-fix: Should fixable issues be corrected automatically?
2. Run Validation
Execute the validation command:
prprompts validate <path> --config <preset> --format <format>
Example:
prprompts validate ./flutter-app --config strict --format html --fix
3. Show Results
Display validation results with clear formatting:
🔍 Validation Results
┌──────────────────────────────────────┐
│ Score: 85/100 │
│ Grade: B │
└──────────────────────────────────────┘
📊 Detailed Scores:
┌────────────────┬───────┬───────┐
│ Category │ Score │ Grade │
├────────────────┼───────┼───────┤
│ Code Quality │ 90/100│ A │
│ Security │ 100/100│ A │
│ Performance │ 75/100│ C │
│ Accessibility │ 65/100│ D │
│ Architecture │ 88/100│ B │
└────────────────┴───────┴───────┘
⚠️ Issues Summary:
• Errors: 2
• Warnings: 5
• Info: 8
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 · 365 lines · 0 tokens per session scan A 7a9cd3ca2fa9
validate-flutter is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,250 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-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.bug.pr
Open a pull request for the applied bug fix, linking the tracked issue.
speckit.chore.issue
File a GitHub issue from a chore assessment (the 'report' phase) and record the issue link.
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.