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/fujigo-software/f5-framework-claude/f5-bagit 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-ba)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-ba"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-ba.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.00003 | $0.06499 |
| Opus 5 | $0.00002 | $0.03249 |
| Sonnet 5 | $0.00001 | $0.01300 |
| Haiku 4.5 | $0.00000 | $0.00650 |
Grade A, and why
f5-ba 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 5d 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 — 1,048 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/f5-ba - Business Analysis Workflow Command
Manage Business Analysis workflow following BABOK standards, from Enterprise Analysis to Validation & Sign-off.
ARGUMENTS
The user's request is: $ARGUMENTS
⚠️ CRITICAL OUTPUT RULES
BA Workflow files MUST be in .f5/ba-workflow/ NOT in project root or docs/.
BẮT BUỘC tuân theo cấu trúc sau:
| Document Type | Output Path |
|---|---|
| BA Workflow | .f5/ba-workflow/ |
| Phase 1 docs | .f5/ba-workflow/phase-1-enterprise-analysis/ |
| Phase 2 docs | .f5/ba-workflow/phase-2-planning/ |
| Phase 3 docs | .f5/ba-workflow/phase-3-elicitation/ |
| Phase 4 docs | .f5/ba-workflow/phase-4-documentation/ |
| Phase 5 docs | .f5/ba-workflow/phase-5-validation/ |
| Status file | .f5/ba-workflow/status.json |
✅ CORRECT paths:
.f5/ba-workflow/status.json ✅
.f5/ba-workflow/phase-1-enterprise-analysis/stakeholder-map.md ✅
.f5/ba-workflow/phase-4-documentation/documents/srs.md ✅
❌ WRONG paths:
ba-workflow/status.json ❌ (missing .f5/ prefix!)
docs/stakeholder-map.md ❌
phase-1/stakeholder-map.md ❌
BA WORKFLOW OVERVIEW
BA WORKFLOW PHASES
════════════════════════════════════════════════════════════════
Phase 1: Enterprise Analysis
├── Stakeholder Identification
├── Current State Documentation
└── Problem Statement
↓ Gate 1
Phase 2: Requirements Planning
├── Scope Definition
├── Requirements Management Plan
└── Communication Plan
↓ Gate 2
Phase 3: Requirements Elicitation
├── Interviews
├── Workshops
├── Document Analysis
└── Excel Import (from customer)
↓ Gate 3
Phase 4: Analysis & Documentation
├── BRD (Business Requirements Document)
├── SRS (Software Requirements Specification)
└── FRS (Functional Requirements Specification)
↓ Gate 4
Phase 5: Validation & Sign-off
├── Review Sessions
├── Approval Workflow
└── Baseline
↓ Complete
════════════════════════════════════════════════════════════════
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.
- 5d ago First seen · 1,048 lines · 3 tokens per session scan A d80e0dd8a4e3
f5-ba is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 3 tokens to every session and 6,499 once invoked, about $0.0000 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
build
Guided feature development with approval gates at each phase.
plan
Project spec (no args) or feature FRD (with args).
ship
Autonomous spec-to-PR pipeline with zero approval gates.
debug
Structured debugging with parallel investigation agents.
init
Analyze codebase and generate CLAUDE.md with project conventions.
release
Generate changelog, bump version, and create git tag.