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 skills/monkilabs/opencastle/jiranpx skills add monkilabs/opencastle --skill jiragit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/skills/monkilabs/opencastle/jira)<a href="https://agentmods.dev/skills/monkilabs/opencastle/jira"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/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 | $0.00053 | $0.00557 |
| Opus 5 | $0.00026 | $0.00279 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
jira-management 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 5d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management with Jira
Project keys, workflow state IDs, and board config: tracker-config.md. Docs: https://developer.atlassian.com/cloud/jira/platform/
Gotchas
- Transitions are constrained by the project's workflow — a jump the board does not allow fails even with a valid status name. Read the workflow state IDs from
tracker-config.mdbefore transitioning; retry once, then stop. - Status names in JQL must be quoted when they contain spaces:
status = "In Progress". - A
createcall is only successful if it returns an issue key. Verify before treating the issue as tracked. - PR-driven status updates only happen when the GitHub/Jira integration is configured; link by putting the key (
PROJ-123) in the branch or PR title.
Conventions
Summary format [Area] Short description — e.g. [Schema] Add priceRange field, [DB] Add price_range column, [UI] Build PriceRangeFilter, [Test] E2E price range filtering.
Every description must carry: Objective (one sentence), Files (partition) (paths this agent may modify), Acceptance Criteria (verifiable checklist), Dependencies (issue keys). Group under an Epic; use components or labels for domain grouping.
Flow Backlog → To Do → In Progress → In Review → Done. Agent moves To Do → In Progress on start, In Progress → Done only after verification.
Untracked bug found mid-task: search Jira first; if absent create a [Bug] in Backlog with symptoms, repro steps, and affected files.
JQL
project = PROJ AND status = "In Progress" ORDER BY priority DESC
project = PROJ AND type = Bug AND status != Done ORDER BY priority DESC
project = PROJ AND sprint in openSprints() ORDER BY priority DESC
project = PROJ AND priority = Highest AND status != Done
Session: query in-progress work first → decompose into issues → link dependencies → transition before/after each → on completion verify all Epic issues Done, run build/lint/test, close the Epic.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 39 lines · 53 tokens per session scan A 6aa42bb446d3
jira-management is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 557 once invoked, about $0.0003 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 skills, from other repositories
jira-ticket-builder
Turns rough input into structured Jira work. Two modes — single-ticket mode turns a bug description, meeting notes, Slack thread, incident writeup, or a few sentences into one fully-structured Jira ticket; decomposition mode turns a rough requirements doc or product brief with multiple asks and open questions into…
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
find-code-tasks
Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.
linear
Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.
product-architect
Complete product development system with 80 agents and 36 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
tsk-add
Queue a single task based on the current conversation using tsk add.