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 CloudChef/atlasclaw-providers --skill jira-issuegit clone --depth 1 https://github.com/CloudChef/atlasclaw-providersWrote 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/cloudchef/atlasclaw-providers/jira-issue)<a href="https://agentmods.dev/skills/cloudchef/atlasclaw-providers/jira-issue"><img src="https://agentmods.dev/badge/skills/cloudchef/atlasclaw-providers/jira-issue/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/cloudchef/atlasclaw-providers/jira-issue"><img src="https://agentmods.dev/badge/skills/cloudchef/atlasclaw-providers/jira-issue.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.00027 | $0.00687 |
| Opus 5 | $0.00014 | $0.00344 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
jira-issue 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
jira-issue
This is a provider skill under providers/jira/skills/jira-issue.
Purpose
Handle Jira Issue CRUD by orchestrating local scripts in scripts/ that call Jira REST API.
Trigger Conditions
Use this skill when user intent is any of:
- Create issue / report bug / log incident
- Get issue details
- Update issue fields
- Delete issue
Script Entry Points
scripts/create_issue.pyscripts/get_issue.pyscripts/update_issue.pyscripts/delete_issue.py
Invocation Guidance
When the user says:
- "Create a Jira issue for service startup failure"
Construct and run:
python app/atlasclaw/providers/jira/skills/jira-issue/scripts/create_issue.py \
--summary "Service startup failure" \
--description "Service failed to start due to a database connection timeout"
Then return created issue key to user.
Notes
- Scripts read Jira connection from
atlasclaw.json(service_providers.jira). - API mappings are in
references/api_mapping.md. - Skill scripts are part of this skill package, not standalone global skills.
What ships with it
11 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.
- references/api_mapping.md 580 B
- scripts/_common.py 3.8 KB runs code
- scripts/_jira_client.py 3.6 KB runs code
- scripts/create_issue.py 3.2 KB runs code
- scripts/delete_issue.py 1014 B runs code
- scripts/get_issue.py 1.2 KB runs code
- scripts/jira_issue_create.py 4.1 KB runs code
- scripts/jira_issue_delete.py 1.5 KB runs code
- scripts/jira_issue_get.py 1.9 KB runs code
- scripts/jira_issue_update.py 2.1 KB runs code
- scripts/update_issue.py 1.5 KB runs code
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 · 107 lines · 27 tokens per session scan A 910416332374
jira-issue is a skill published in the GitHub repository CloudChef/atlasclaw-providers (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 687 once invoked, about $0.0001 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
agent-swarm
Agent skill for swarm - invoke with $agent-swarm.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
task-management
Use before any Worker taskflow call or assigned-task workflow, including reading task state, acknowledging a task, executing a task, tracking progress, handling blockers/questions, submitting structured results, or reporting completion. Always use this skill when the message mentions assigned task, task ID…
task-coordination
Coordinate access to shared task directories using .processing marker files. Use before accessing a Worker's workspace to prevent conflicts when both Manager and Worker might modify files simultaneously.
project-management
Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution.