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-migrategit 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-migrate)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-migrate"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-migrate.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.00006 | $0.02434 |
| Opus 5 | $0.00003 | $0.01217 |
| Sonnet 5 | $0.00001 | $0.00487 |
| Haiku 4.5 | $0.00001 | $0.00243 |
Grade A, and why
f5-migrate 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/f5-migrate - Structure Migration
Migrate F5 project structure between versions.
ARGUMENTS
The user's request is: $ARGUMENTS
PURPOSE
Migrate handles:
- Version upgrades (v1.x → v2.x)
- Structure reorganization
- Configuration format changes
- Breaking changes adaptation
MIGRATION TYPES
| Type | Description | Example |
|---|---|---|
version |
Framework version upgrade | v1.2 → v2.0 |
structure |
Directory reorganization | .claude/f5/ → .f5/ |
config |
Configuration format | YAML → JSON |
commands |
Slash command updates | New command format |
ACTIONS
Check Migration Status
/f5-migrate status
Output:
📊 Migration Status
Current Version: 1.2.0
Latest Version: 2.0.0
Available Migrations:
1.2.0 → 1.3.0 Minor updates, config additions
1.3.0 → 2.0.0 Major restructure (BREAKING)
Breaking Changes in 2.0.0:
• .claude/f5/ moved to .f5/
• config.yaml replaced with config.json
• New quality gates structure
• Updated command format
Run /f5-migrate plan for detailed migration plan.
Create Migration Plan
/f5-migrate plan
Output:
📋 Migration Plan: 1.2.0 → 2.0.0
PHASE 1: Backup
□ Create backup of .claude/f5/
□ Export current configuration
□ Save memory files
PHASE 2: Structure Migration
□ Create .f5/ directory
□ Move config files
□ Migrate memory system
□ Update file references
PHASE 3: Configuration Migration
□ Convert config.yaml to config.json
□ Update schema to v2.0
□ Migrate custom settings
PHASE 4: Command Updates
□ Update slash command references
□ Migrate custom commands
□ Update CLAUDE.md
PHASE 5: Validation
□ Verify all files migrated
□ Test configuration loading
□ Validate gate status
Estimated changes:
Files moved: 15
Files updated: 8
New files: 5
Run /f5-migrate execute to start migration.
Execute Migration
/f5-migrate execute
Output:
🚀 Starting Migration: 1.2.0 → 2.0.0
[Phase 1: Backup]
✓ Created backup at .f5-backup-20240115/
✓ Exported configuration
✓ Saved 4 memory files
[Phase 2: Structure Migration]
✓ Created .f5/ directory
✓ Moved config files (3 files)
✓ Migrated memory system (4 files)
✓ Updated file references
[Phase 3: Configuration Migration]
✓ Converted config.yaml to config.json
✓ Updated schema to v2.0
✓ Preserved custom settings
[Phase 4: Command Updates]
✓ Updated 12 slash command references
✓ Migrated 2 custom commands
✓ Regenerated CLAUDE.md
[Phase 5: Validation]
✓ All 15 files migrated successfully
✓ Configuration loads correctly
✓ Gate status preserved
═══════════════════════════════════════════════════════════
✓ Migration completed successfully!
New version: 2.0.0
Backup location: .f5-backup-20240115/
Next steps:
1. Review migrated files
2. Run /f5-status to verify
3. Delete backup when satisfied
═══════════════════════════════════════════════════════════
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 · 461 lines · 6 tokens per session scan A b467b905756c
f5-migrate is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 2,434 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.