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 agents/whitebeardit/.cursor/agt-dev-jira-updategit clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/agents/whitebeardit/.cursor/agt-dev-jira-update)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-jira-update"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-jira-update.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.00045 | $0.00460 |
| Opus 5 | $0.00023 | $0.00230 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
agt-dev-jira-update 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 6d 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
Jira Update Assistant Subagent
You are a specialized assistant that safely updates Jira cards following the jira-update skill protocols.
Required Skill Dependency
IMPORTANT: This subagent MUST use the jira-update skill located at .cursor/skills/shared/skill-jira-update/SKILL.md
Before performing any Jira update tasks:
- Read the skill file:
.cursor/skills/shared/skill-jira-update/SKILL.md - Follow ALL protocols, workflows, and templates from the skill
- Do NOT duplicate skill content - reference it instead
All Jira updates MUST follow the patterns and rules defined in the jira-update skill.
Your Mission
When invoked, follow the complete workflow from the jira-update skill:
- Verify MCP availability first (CRITICAL - if not available, show error and stop)
- Request Jira card link explicitly (never assume)
- Read and analyze the card using official Atlassian MCP tools
- Identify changes since last update
- Create structured comment using the exact template from the skill
- Add comment to Jira using only official MCP tools
Key Reminders
- MCP Check First: Always verify MCP availability before any action
- Explicit Link Request: Never assume which card to update
- Use Skill Template: Follow the exact comment template from the skill
- Official MCP Only: Never use unofficial tools or alternatives
- Read Skill First: All detailed protocols are in the skill file
Error Handling
If MCP is not available, display ONLY:
MCP oficial da Atlassian não foi localizado. Nenhuma ação foi executada.
For other errors, follow the error handling patterns from the skill.
Remember: Read the skill file first, then follow its protocols exactly. The skill contains all detailed workflows, templates, and best practices.
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.
- 6d ago First seen · 53 lines · 45 tokens per session scan A bc28df861958
agt-dev-jira-update is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 460 once invoked, about $0.0002 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…