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 ihudak/ihudak-claude-plugins --skill acligit clone --depth 1 https://github.com/ihudak/ihudak-claude-pluginsWrote 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/ihudak/ihudak-claude-plugins/acli)<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/acli"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/acli/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/ihudak/ihudak-claude-plugins/acli"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/acli.svg" alt="Reviewed on agentmods" width="80" 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.00082 | $0.03702 |
| Opus 5 | $0.00041 | $0.01851 |
| Sonnet 5 | $0.00016 | $0.00740 |
| Haiku 4.5 | $0.00008 | $0.00370 |
Grade A, and why
acli 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.
How it starts
The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian CLI (acli)
Interact with Atlassian Cloud — Jira work items, projects, sprints, boards, filters, and
Confluence content — using the acli CLI.
Prerequisites
-
aclimust be installed (acli --versionto check) and authenticated- OAuth (Jira + Confluence together):
acli auth login - Product-scoped OAuth:
acli jira auth login --web/acli confluence auth login - API token:
acli jira auth login --site <site>.atlassian.net --email <you>@... --token - Verify with
acli auth status(global) oracli jira auth status/acli confluence auth status
- OAuth (Jira + Confluence together):
-
For multi-account setups, switch the active account with
acli jira auth switch/acli confluence auth switch -
Headless environments (containers, CI, remote shells):
--webOAuth cannot complete, because the callback is a loopback URL only a browser on the same machine can open. Use the API-token form and feed the token on stdin:echo "$ATLASSIAN_API_TOKEN" | acli jira auth login \ --site "<site>.atlassian.net" --email "<you>@example.com" --tokenaclistores profiles and credentials under~/.config/acli, so wherever that directory persists, one login serves every later session. -
Never pass a token as a command-line argument. It lands in shell history and in the process list. Pipe it on stdin as above, never echo it back into the conversation, and never write it to a file in the repository.
Note:
aclihas no global--site/--accountflag. The active account is chosen viaacli <product> auth switch. Targeting a different project is done per-command with--project/--key, not a global flag.
Safety
acli writes to live Jira and Confluence. Ask the user before running anything below, and never
add --yes/-y on your own initiative — its only purpose is to skip the confirmation prompt that
exists to protect the user.
Irreversible: jira workitem delete, jira project delete, jira sprint delete,
jira board delete, jira field delete, jira workitem comment delete,
jira workitem attachment delete, confluence space delete.
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 · 331 lines · 82 tokens per session scan A 967e688c60ae
acli is a skill published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 3,702 once invoked, about $0.0004 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-31.
Other skills, from other repositories
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
wwas
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
using-flywheel
Operate the Agentic Coding Flywheel as a caller-selected software factory; keep its runtime state out of AgentOps verdicts. Triggers: "using flywheel", "agent flywheel".
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.