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-jira-issue)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-jira-issue"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-jira-issue.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.1 | $0.00011 | $0.00181 |
| Opus 5 | $0.00005 | $0.00090 |
| Sonnet 5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
f5-jira-issue 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 8d 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
⚠️ DEPRECATED: /f5-jira-issue
This command has been consolidated into /f5-jira issue.
Migration
# Old (deprecated)
/f5-jira-issue list
/f5-jira-issue get PROJ-123
/f5-jira-issue create "Bug title"
# New (use this instead)
/f5-jira issue list
/f5-jira issue get PROJ-123
/f5-jira issue create "Bug title"
/f5-jira issue update PROJ-123
/f5-jira issue link PROJ-123 PROJ-456
Automatic Redirect
Executing /f5-jira issue $ARGUMENTS...
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.
- 8d ago First seen · 29 lines · 11 tokens per session scan A e780130e7942
f5-jira-issue is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 181 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
ralph-build
Implement the next task from the queue.
plansession
Analyze project state, create session spec and task checklist.
updateprd
Mark session complete and sync documentation.
paul:add-phase
Add a new phase to current milestone.
debug
Structured debugging with parallel investigation agents.
ia-lfg
Full autonomous engineering workflow (plan, build, review, ship).