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)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-jira"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-jira.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.00015 | $0.02897 |
| Opus 5 | $0.00008 | $0.01448 |
| Sonnet 5 | $0.00003 | $0.00579 |
| Haiku 4.5 | $0.00002 | $0.00290 |
Grade A, and why
f5-jira 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.
How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/f5-jira - Unified Jira Integration
Consolidated command for all Jira operations. Replaces:
- f5-jira-setup →
/f5-jira setup - f5-jira-sync →
/f5-jira sync - f5-jira-status →
/f5-jira status - f5-jira-convert →
/f5-jira convert - f5-jira-issue →
/f5-jira issue - f5-jira-attachments →
/f5-jira attachments
ARGUMENTS
$ARGUMENTS
STEP 1: DETECT SUBCOMMAND
Parse the request to determine action:
| Pattern | Subcommand | Description |
|---|---|---|
setup, config, cấu hình |
SETUP | Configure Jira connection |
file path (.xlsx, .csv) |
SYNC_FILE | Sync specific file to Jira |
sync, đồng bộ (no file) |
SYNC | Sync all pending issues |
status, check, kiểm tra |
STATUS | Show integration status |
convert |
CONVERT | Convert Excel → Jira format |
issue + action |
ISSUE | CRUD operations on issues |
attachments, images, ảnh |
ATTACHMENTS | Manage attachments |
| (empty/default) | STATUS | Show status overview |
SUBCOMMAND: SETUP
Configure Jira connection. Interactive wizard or manual config.
Usage
/f5-jira setup # Interactive wizard
/f5-jira setup --cloud # Jira Cloud guide
/f5-jira setup --server # Jira Server/DC guide
/f5-jira setup --test # Test connection
Interactive Setup Flow
# Check if already configured
if [ -f ".f5/integrations.json" ]; then
CONFIGURED=$(jq -r '.jira.configured // false' .f5/integrations.json 2>/dev/null)
if [ "$CONFIGURED" == "true" ]; then
echo "✅ Jira already configured"
jq '.jira | {url, project, email}' .f5/integrations.json
echo ""
echo "Run '/f5-jira setup --force' to reconfigure"
exit 0
fi
fi
# Run setup wizard
f5 jira setup
Jira Cloud Setup Guide
## Jira Cloud Setup
1. **Get API Token:**
https://id.atlassian.com/manage-profile/security/api-tokens
2. **Run Setup:**
```bash
f5 jira setup
- Enter credentials:
- URL:
https://your-domain.atlassian.net - Email:
[email protected] - Token:
<your-api-token> - Project:
PROJECT_KEY
- URL:
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 · 500 lines · 15 tokens per session scan A 49559cdab35f
f5-jira is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 2,897 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).