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 skills add grandcamel/JIRA-Assistant-Skills --skill jira-admingit clone --depth 1 https://github.com/grandcamel/JIRA-Assistant-SkillsWrote 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/grandcamel/jira-assistant-skills/jira-admin)<a href="https://agentmods.dev/skills/grandcamel/jira-assistant-skills/jira-admin"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-admin/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/skills/grandcamel/jira-assistant-skills/jira-admin"><img src="https://agentmods.dev/badge/skills/grandcamel/jira-assistant-skills/jira-admin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.03752 |
| Opus 5 | $0.00026 | $0.01876 |
| Sonnet 5 | $0.00010 | $0.00750 |
| Haiku 4.5 | $0.00005 | $0.00375 |
Grade A, and why
jira-administration 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- jira-administration — 97% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JIRA Admin Skill
Comprehensive administration tools for JIRA Cloud covering 8 major subsystems.
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| List/get (any resource) | - |
Read-only |
| Search users | - |
Read-only |
| Check permissions | - |
Read-only |
| Create project | - |
Easily reversible (can delete) |
| Create group | - |
Easily reversible (can delete) |
| Create permission/notification scheme | - |
Can delete |
| Create issue type | - |
Can delete |
| Update project settings | ! |
Can be undone |
| Update permission scheme | ! |
Can be modified |
| Enable/disable automation | ! |
Can toggle back |
| Invoke automation rule | ! |
Rule executes; effects vary |
| Add user to group/role | ! |
Can remove |
| Remove user from group/role | ! |
Can re-add |
| Assign scheme to project | ! |
Can reassign |
| Archive project | ! |
Can restore |
| Add/remove screen fields | ! |
Can reverse |
| Delete issue type | !! |
Issues lose type |
| Delete group | !! |
Members lose group access |
| Delete permission scheme | !! |
Projects lose permissions |
| Delete project | !!! |
IRREVERSIBLE - all issues lost |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
CRITICAL: Project deletion is irreversible. Always use --dry-run when available.
What This Skill Does
8 Major Administration Areas:
| Area | Key Operations |
|---|---|
| Project Management | Create, configure, archive, restore projects and categories |
| Automation Rules | Discover, manage, invoke automation rules and templates |
| Permission Schemes | Control who can do what across projects |
| Permission Diagnostics | Check permissions, diagnose 403 errors |
| User & Group Management | Find users, create groups, manage membership |
| Notification Schemes | Configure who receives what notifications |
| Screen Management | Control which fields appear in issue workflows |
| Issue Types & Schemes | Define work item types and their availability |
| Workflow Management | Explore and assign issue lifecycle workflows |
What ships with it
17 files 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.
- assets/templates/notification_scheme_basic.json 778 B
- assets/templates/notification_scheme_comprehensive.json 1.8 KB
- assets/templates/notification_scheme_minimal.json 395 B
- docs/BEST_PRACTICES.md 28 KB
- docs/DECISION-TREE.md 12 KB
- docs/QUICK-REFERENCE.md 12 KB
- docs/subsystems/automation-rules-guide.md 6.6 KB
- docs/subsystems/issue-type-schemes-guide.md 7.7 KB
- docs/subsystems/issue-types-guide.md 4.9 KB
- docs/subsystems/notification-schemes-guide.md 8.6 KB
- docs/subsystems/permission-schemes-guide.md 7.1 KB
- docs/subsystems/project-management-guide.md 6.6 KB
- docs/subsystems/screen-management-guide.md 7.4 KB
- docs/subsystems/user-group-guide.md 5.4 KB
- docs/subsystems/workflow-management-guide.md 9.8 KB
- docs/VOODOO_CONSTANTS.md 9.3 KB
- docs/WORKFLOWS.md 11 KB
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.
- 12d ago First seen · 443 lines · 51 tokens per session scan A 389c8c66e1ab
jira-administration is a skill published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 3,752 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
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
reality-strategy
Change a blocked real-life or organisational situation by recovering the original result, reconstructing real participants and flows, investigating the sustaining cause, mapping stakeholders and practical power, then altering defaults, burdens, incentives, coalitions, information flow, decision rights or action…
mk:jira
Routing skill — recommends the correct mk:jira- leaf for any Jira task. Triggers: 'jira', 'jira ticket', ambiguous Jira intent. NOT an executor — every actual operation forks via a leaf skill.
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.