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-sync)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-jira-sync"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-jira-sync.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.00157 |
| Opus 5 | $0.00005 | $0.00078 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
f5-jira-sync 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-sync
This command has been consolidated into /f5-jira sync.
Migration
# Old (deprecated)
/f5-jira-sync
/f5-jira-sync requirements.xlsx
/f5-jira-sync --dry-run
# New (use this instead)
/f5-jira sync
/f5-jira sync requirements.xlsx
/f5-jira sync --dry-run
/f5-jira sync --push
/f5-jira sync --pull
Automatic Redirect
Executing /f5-jira sync $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 ed04892147d5
f5-jira-sync 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 157 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
plan
Project spec (no args) or feature FRD (with args).
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.
docs
Generate or update project documentation from codebase and specs.
review
Multi-agent code review with parallel validation.