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-initgit 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-init)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-init"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-init.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.00018 | $0.00423 |
| Opus 5 | $0.00009 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
f5-init 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.
What it actually says
F5 Framework Initialization
Initialize the F5 Framework in the current workspace.
What This Command Does
-
Copies Framework Configs from plugin cache to workspace
.f5/directory:manifest.yaml- Framework version and component trackingconfig/- Agent configs, gate definitions, session managementgates/- Quality gate templatesschemas/- YAML validation schemastemplates/- Project templatestdd/- TDD configurationselftest/- Self-test definitionsci/- CI integration scripts
-
Creates Workspace Structure:
.f5/ ├── manifest.yaml ├── config/ ├── gates/ ├── schemas/ ├── templates/ ├── tdd/ ├── selftest/ └── ci/ -
Initializes Team Config (if not exists):
- Creates
.f5/team/team.yamltemplate
- Creates
Usage
# Standard initialization
/f5-init
# Force re-initialization (overwrites existing)
/f5-init force=true
Post-Initialization
After running /f5-init:
- Review
.f5/config/settings - Customize gate definitions in
.f5/gates/if needed - Configure team settings in
.f5/team/team.yaml - Run
/f5-statusto verify setup
Notes
- Existing workspace
.f5/will NOT be overwritten unlessforce=true - Plugin configs are the "factory defaults" - customize workspace copies as needed
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 · 66 lines · 18 tokens per session scan A 9cc3520ea0af
f5-init is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 423 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
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.