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 opendatahub-io/ai-helpers --skill acli-setup-checkgit clone --depth 1 https://github.com/opendatahub-io/ai-helpersWrote 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/opendatahub-io/ai-helpers/acli-setup-check)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/acli-setup-check"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/acli-setup-check/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/opendatahub-io/ai-helpers/acli-setup-check"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/acli-setup-check.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.00045 | $0.00591 |
| Opus 5 | $0.00023 | $0.00296 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
acli-setup-check 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 11d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ACLi Setup Check
Verify that the acli CLI tool is installed, authenticated, and can access Jira.
Implementation
Step 1: Check if acli is Installed
Run the following command to check if acli is available:
which acli
If the command returns a path (e.g., /usr/local/bin/acli), proceed to Step 2.
If the command returns nothing or "not found":
- Inform the user that acli is not installed
- Provide installation instructions:
acli is not installed. Please install it from: https://developer.atlassian.com/cloud/acli/guides/install-acli/ After installation, run: acli jira auth - Stop execution
Step 2: Test Authentication
Test if acli is authenticated by checking the authentication status:
acli jira auth status 2>&1
This command checks if acli is authenticated and can reach the Jira server without requiring access to specific projects.
Analyze the output:
- Success: If the command shows "✓ Authenticated" along with site and email details, authentication is working. Proceed to Step 3.
- Authentication Error: If the output indicates no authentication or invalid credentials:
- Inform the user that authentication has failed
- Guide them to run:
acli jira auth - Explain they'll need their Jira API token from https://id.atlassian.com/manage-profile/security/api-tokens
- Stop execution
Step 3: Report Success
If authentication is successful, report success to the user:
✓ acli is installed and authenticated
✓ Connected to: https://redhat.atlassian.net
You're ready to use acli-based Jira skills!
Error Handling
- acli not found: Provide installation instructions and stop
- Authentication failure: Guide user to run
acli jira authand stop - Network errors: Report the error and suggest checking network connectivity
- Permission denied: Inform user they may not have access to the queried projects
Examples
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.
- 11d ago First seen · 90 lines · 45 tokens per session scan A 5e8d93dd4cf7
acli-setup-check is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 4d ago), licensed Apache-2.0. It adds 45 tokens to every session and 591 once invoked, about $0.0002 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…