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/implement-nextgit 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/implement-next)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/implement-next"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/implement-next.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.03035 |
| Opus 5 | $0.00000 | $0.01517 |
| Sonnet 5 | $0.00000 | $0.00607 |
| Haiku 4.5 | $0.00000 | $0.00303 |
Grade A, and why
implement-next 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 — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EXECUTE: Implement Next Feature
IMPORTANT: This is an EXECUTION command. Immediately start implementing without waiting for confirmation.
Auto-implement the next pending task from IMPLEMENTATION_PLAN.md with tests, validation, and progress tracking.
STEP 1: Find Next Task
Read docs/IMPLEMENTATION_PLAN.md and find the first task marked [TODO].
Priority order:
- Tasks on critical path (check "Critical Path" section)
- Tasks with no dependencies
- First [TODO] task in current sprint
If no TODO tasks found:
✅ All tasks complete!
Run:
/update-plan # Update velocity metrics
/qa-check # Final compliance audit
STEP 2: Check Dependencies
For the selected task, check its Dependencies field:
**Dependencies**: Task 1.1 (DONE), Task 1.2 (IN_PROGRESS)
If any dependency is [TODO] or [BLOCKED]:
⚠️ Cannot start Task X.Y: Dependencies not ready
Blocked by:
- Task 1.2: [IN_PROGRESS] (expected completion: 2 hours)
Skipping to next available task...
Find next task with all dependencies [DONE].
STEP 3: Mark Task IN_PROGRESS
BEFORE implementing, update the task status:
Change:
### Task 2.1: Dashboard - Domain Layer [TODO]
To:
### Task 2.1: Dashboard - Domain Layer [IN_PROGRESS]
**Started**: 2025-02-05 10:30 AM
Also update subtasks:
**Subtasks**:
- [ ] 2.1.1 Create User entity
- [ ] 2.1.2 Create UserRepository interface
This signals to other developers that this task is being worked on.
STEP 4: Load Relevant PRPROMPTS
Based on the task's PRPROMPTS field, read referenced files:
**PRPROMPTS**: @PRPROMPTS/01-feature_scaffold.md, @PRPROMPTS/16-security_and_compliance.md
Read:
- @PRPROMPTS/01-feature_scaffold.md
- @PRPROMPTS/16-security_and_compliance.md
- @PRPROMPTS/03-bloc_implementation.md (if presentation layer)
- @PRPROMPTS/04-api_integration.md (if API involved)
- @PRPROMPTS/05-testing_strategy.md (always)
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 · 470 lines · 0 tokens per session scan A 5958931c425f
implement-next 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 3,035 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.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.
speckit.bug.pr
Open a pull request for the applied bug fix, linking the tracked issue.