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/carloshpdoc/ios-workflow-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/carloshpdoc/ios-workflow-claude/update-jira)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/update-jira"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/update-jira/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/update-jira"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/update-jira.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
update-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 9d 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
Update Jira Task
Project context: Values in angle brackets below (e.g.
<scheme>,<JIRA_KEY>,<flag-key-enum>) are resolved at runtime — detect them from the project (xcodebuild -list -jsonfor the scheme,git/ghfor repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.
Update a Jira task with a summary of the fix implementation.
Usage
/update-jira <task_id>
Arguments:
task_id- The Jira task ID (e.g., PROD-4070, <JIRA_KEY>-XXXX)
Examples:
/update-jira PROD-4070
/update-jira <JIRA_KEY>-XXXX
Instructions
When this skill is invoked:
-
Parse the task ID from
$ARGUMENTS -
Gather context from the current session:
- Check git log for recent commits on current branch
- Check for any open PRs from current branch using
gh pr view - Identify changed files from commits
-
Build the update comment with:
- PR link (if available)
- Problem summary - What was the issue
- Solution summary - How it was fixed
- Files changed - List of modified files
- Result - What the fix accomplishes
-
Post comment to Jira:
- Use
mcp__claude_ai_Atlassian__addCommentToJiraIssue - cloudId:
<jira-host> - issueIdOrKey: the task ID
- contentFormat:
markdown
- Use
-
Confirm success with link to Jira task
Comment Template
## Fix Implemented
**PR:** <pr_url>
### Problem
<brief description of the issue>
### Solution
<what was changed and why>
### Files Changed
- <file1>
- <file2>
### Result
<what the fix accomplishes>
Notes
- Extracts information from git history and PR details automatically
- Uses the current branch context to determine what was done
- Keep descriptions concise but informative
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.
- 9d ago First seen · 74 lines · 0 tokens per session scan A e68d994f6554
update-jira is a command published in the GitHub repository carloshpdoc/ios-workflow-claude (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 497 tokens. 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-31.
Other commands, from other repositories
ijfw-status
Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
fest-list
List all festivals with their status and completion percentage.