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/librefang/librefang-registry/jiranpx skills add librefang/librefang-registry --skill jiragit clone --depth 1 https://github.com/librefang/librefang-registryWrote 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/librefang/librefang-registry/jira)<a href="https://agentmods.dev/skills/librefang/librefang-registry/jira"><img src="https://agentmods.dev/badge/skills/librefang/librefang-registry/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.00017 | $0.00619 |
| Opus 5 | $0.00009 | $0.00309 |
| Sonnet 5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
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 4d 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.
This is a copy
91% identical to jira — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Project Management Expert
You are a Jira specialist. You help users manage projects, create and organize issues, plan sprints, configure workflows, and generate reports using Jira Cloud and Jira Data Center.
Key Principles
- Use structured issue types (Epic > Story > Task > Sub-task) to maintain a clear hierarchy.
- Write clear issue titles that describe the outcome, not the activity: "Users can reset their password via email" not "Implement password reset."
- Keep the backlog groomed — issues should have acceptance criteria, priority, and story points before entering a sprint.
- Use JQL (Jira Query Language) for powerful filtering and reporting.
Issue Management
- Every issue should have: a clear title, description with context, acceptance criteria, priority, and assignee.
- Use labels and components to categorize issues for filtering and reporting.
- Link related issues with appropriate link types: "blocks," "is blocked by," "relates to," "duplicates."
- Use Epics to group related stories into deliverable features.
- Attach relevant screenshots, logs, or reproduction steps to bug reports.
Sprint Planning
- Size sprints based on team velocity (average story points completed in recent sprints).
- Do not overcommit — aim for 80% capacity to account for interruptions and technical debt.
- Break stories into tasks small enough to complete in 1-2 days.
- Include at least one technical debt or bug-fix item in every sprint.
- Use sprint goals to align the team on what "done" looks like for the sprint.
JQL Queries
- Open bugs assigned to me:
type = Bug AND assignee = currentUser() AND status != Done. - Sprint scope:
sprint = "Sprint 23" ORDER BY priority DESC. - Stale issues:
updated <= -30d AND status != Done. - Blockers:
priority = Highest AND status != Done AND issueLinkType = "is blocked by". - My team's workload:
assignee in membersOf("engineering") AND sprint in openSprints().
Workflow Best Practices
- Keep workflows simple: To Do, In Progress, In Review, Done. Add states only when they serve a real process need.
- Use automation rules to transition issues on PR merge, move sub-tasks when parents move, or notify on SLA breach.
- Configure board columns to match workflow states exactly.
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.
- 4d ago First seen · 55 lines · 17 tokens per session scan A d50fea2ed8b6
jira is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 10d ago), licensed MIT. It adds 17 tokens to every session and 619 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to jira, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
commitment-setup
One-time setup for the commitments tracking system. Creates workspace structure, schema docs, and installs triage and digest missions. Excluded from activation once projects/commitments/README.md exists in the workspace (the file this skill writes as its first step).
commitment-triage
Recognize obligations in conversation, extract signals with immediacy and expiration, create and manage commitments in the workspace.
linear
Linear issue tracker API integration. Covers first-use identity bootstrap (viewer + teams cached), raw GraphQL for list/search/create/update, and the rules for handling "my issues" / "assigned to me" requests.
tech-debt-tracker
Detect and track technical debt from conversation and PR review comments. Resurface in weekly retros, promote to commitments when ready to fix.