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.
git clone --depth 1 https://github.com/Fujigo-Software/f5-framework-claudeWrote 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/fujigo-software/f5-framework-claude/f5-planning)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-planning"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-planning/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/commands/fujigo-software/f5-framework-claude/f5-planning"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-planning.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.00006 | $0.02781 |
| Opus 5.5 | $0.00002 | $0.01112 |
| Sonnet 5.5 | $0.00001 | $0.00556 |
| Haiku 4.5 | $0.00001 | $0.00278 |
Grade A, and why
f5-planning 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 1mo 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/f5-planning - Project Planning & WBS Command
Generate Work Breakdown Structure (WBS), estimates, and sprint planning.
ARGUMENTS
The user's request is: $ARGUMENTS
⚠️ CRITICAL OUTPUT RULES
Output files MUST be in .f5/planning/
| Document Type | Output Path |
|---|---|
| WBS | .f5/planning/wbs.md |
| Estimates | .f5/planning/estimates.md |
| Sprint Plan | .f5/planning/sprints/sprint-{N}.md |
| Roadmap | .f5/planning/roadmap.md |
| Resource Plan | .f5/planning/resources.md |
❌ WRONG paths:
docs/wbs.md ❌
planning.md ❌
wbs.md ❌
STEP 1: PARSE ACTION
| Action | Description |
|---|---|
wbs |
Generate Work Breakdown Structure |
estimate |
Estimate effort for tasks |
sprint |
Create sprint plan |
roadmap |
Generate project roadmap |
resource |
Resource allocation plan |
status |
Show planning status |
ACTION: WBS
/f5-planning wbs [--from <source>]
Sources
srs- Generate from SRS requirements (default)design- Generate from design documentsscreens- Generate from screen list
Process
- Read SRS from
.f5/specs/srs/v1.0.0/srs.md - Read Screen List from
.f5/specs/basic-design/v1.0.0/screens/screen-list.md - Read API Design from
.f5/specs/basic-design/v1.0.0/api/api-design.md - Generate hierarchical WBS
- Output to
.f5/planning/wbs.md
Output Template
# Work Breakdown Structure (WBS)
**Project:** {{PROJECT_NAME}}
**Generated:** {{TIMESTAMP}}
**Source:** {{SOURCE}}
## Summary
| Category | Items | Estimated Days |
|----------|-------|----------------|
| Backend | {{COUNT}} | {{DAYS}} |
| Frontend | {{COUNT}} | {{DAYS}} |
| Mobile | {{COUNT}} | {{DAYS}} |
| DevOps | {{COUNT}} | {{DAYS}} |
| **Total** | {{TOTAL}} | {{TOTAL_DAYS}} |
---
## 1. Backend Development
### 1.1 Authentication Module
| ID | Task | Priority | Est. Days | Dependencies |
|----|------|----------|-----------|--------------|
| BE-AUTH-001 | User Registration API | P0 | 1 | - |
| BE-AUTH-002 | OTP Verification | P0 | 0.5 | BE-AUTH-001 |
| BE-AUTH-003 | Login API | P0 | 0.5 | BE-AUTH-001 |
| BE-AUTH-004 | JWT Token Management | P0 | 1 | BE-AUTH-003 |
| BE-AUTH-005 | Password Reset | P1 | 0.5 | BE-AUTH-001 |
### 1.2 Listing Module
| ID | Task | Priority | Est. Days | Dependencies |
|----|------|----------|-----------|--------------|
| BE-LIST-001 | Create Listing API | P0 | 1.5 | BE-AUTH |
| BE-LIST-002 | Search & Filter API | P0 | 2 | BE-LIST-001 |
| BE-LIST-003 | Listing Detail API | P0 | 0.5 | BE-LIST-001 |
### 1.3 Auction Module
...
### 1.4 Order Module
...
### 1.5 Payment Module
...
---
## 2. Frontend Development (Web)
### 2.1 Authentication Screens
| ID | Task | Priority | Est. Days | Dependencies |
|----|------|----------|-----------|--------------|
| FE-AUTH-001 | Login Screen | P0 | 1 | BE-AUTH-003 |
| FE-AUTH-002 | Register Screen | P0 | 1 | BE-AUTH-001 |
| FE-AUTH-003 | OTP Screen | P0 | 0.5 | BE-AUTH-002 |
### 2.2 Listing Screens
...
---
## 3. Mobile Development (Flutter)
### 3.1 Authentication Screens
...
### 3.2 Farmer Screens
...
### 3.3 Buyer Screens
...
---
## 4. DevOps & Infrastructure
### 4.1 Initial Setup
| ID | Task | Priority | Est. Days | Dependencies |
|----|------|----------|-----------|--------------|
| DO-001 | Docker setup | P0 | 0.5 | - |
| DO-002 | CI/CD Pipeline | P0 | 1 | DO-001 |
| DO-003 | Database setup | P0 | 0.5 | DO-001 |
---
## 5. Testing
### 5.1 Unit Tests
...
### 5.2 Integration Tests
...
### 5.3 E2E Tests
...
---
## Dependencies Graph
```mermaid
graph LR
AUTH[Auth Module] --> LIST[Listing Module]
AUTH --> USER[User Module]
LIST --> AUC[Auction Module]
LIST --> OFFER[Offer Module]
AUC --> ORDER[Order Module]
OFFER --> ORDER
ORDER --> PAY[Payment Module]
ORDER --> QC[Quality Check]
Priority Summary
| Priority | Tasks | Days | % of Total |
|---|---|---|---|
| P0 (MVP) | {{P0_COUNT}} | {{P0_DAYS}} | {{P0_PERCENT}}% |
| P1 (Phase 2) | {{P1_COUNT}} | {{P1_DAYS}} | {{P1_PERCENT}}% |
| P2 (Future) | {{P2_COUNT}} | {{P2_DAYS}} | {{P2_PERCENT}}% |
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.
- 1mo ago First seen · 422 lines · 6 tokens per session scan A f292ebb4c000
f5-planning is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 2,781 once invoked, about $0.0000 per session on Opus 5.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
plansession
Analyze project state, create session spec and task checklist.
updateprd
Mark session complete and sync documentation.
ralph-build
Implement the next task from the queue.
paul:add-phase
Add a new phase to current milestone.
ia-lfg
Full autonomous engineering workflow (plan, build, review, ship).
debug
Structured debugging with parallel investigation agents.