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 CliMA/ClimaAtmos.jl --skill fix-cigit clone --depth 1 https://github.com/CliMA/ClimaAtmos.jlWrote 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/clima/climaatmos.jl/fix-ci)<a href="https://agentmods.dev/skills/clima/climaatmos.jl/fix-ci"><img src="https://agentmods.dev/badge/skills/clima/climaatmos.jl/fix-ci.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 11 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00084 | $0.04852 |
| Opus 5 | $0.00042 | $0.02426 |
| Sonnet 5 | $0.00017 | $0.00970 |
| Haiku 4.5 | $0.00008 | $0.00485 |
Grade A, and why
fix-ci 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 8d 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix CI
The loop:
- At session start: set up CI access (Section 1), verify the local tools (Section 4), and create or re-read the measurement ledger (Section 7).
- Triage every failed job of the latest build — Buildkite
hard_failedsteps and failed GitHub Actions checks (Section 2). After the FIRST complete build of the PR, also run the job-time comparison against main (Section 5.2) — do not wait until correctness work is done. - Fix ONE root cause (Sections 3, 6, 8, 9).
- Verify the fix locally (Section 4).
- If the change is performance-relevant — it touches hot loops, kernels, broadcasting or indexing machinery, type parameters of core structs, or compiler annotations — benchmark against main (Section 5).
- Format, commit, push (Section 2).
- Repeat until CI is green or you reach a decision only the repository owner can make (Section 3).
1. Set up access to CI results before anything else
- GitHub Actions: raw job logs require authentication. Check
gh auth status; ifghis missing or logged out, STOP and ask the user to install and authenticate it (gh auth login). Then:- Statuses:
gh api repos/<org>/<repo>/commits/<sha>/check-runs - Logs:
gh api repos/<org>/<repo>/actions/jobs/<job id>/logs(the check-run id is the job id)
- Statuses:
- Buildkite (CliMA's GPU/MPI CI): public, no auth needed. All endpoints
return JSON with the header
Accept: application/json:- Build state:
https://buildkite.com/<org>/<pipeline>/builds/<N>.json - Steps with outcomes and job ids:
https://buildkite.com/<org>/<pipeline>/builds/<N>/data/steps?exclude_group_steps=true(each step haslabel,outcome—passed/hard_failed/soft_failed—statistics.latest_job_id, andlatest_job_started_at/finished_attimestamps for wall-time comparisons) - Job log:
https://buildkite.com/organizations/<org>/pipelines/<pipeline>/builds/<N>/jobs/<job id>/log(read theoutputfield, strip HTML tags, unescape entities) - Job artifacts (e.g. flame graphs): GET
https://buildkite.com/organizations/<org>/pipelines/<pipeline>/builds/<N>/jobs/<job id>/artifacts, then GET each artifact'surl.
- Build state:
- Map a commit to all of its builds (including extra pipelines like an
end-to-end performance pipeline) via
gh api repos/<org>/<repo>/commits/<sha>/status— each status carries atarget_url. To find a branch's latest build, resolve its head sha first (gh api repos/<org>/<repo>/commits/<branch> --jq .sha).
What ships with it
4 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.
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.
- 8d ago First seen · 356 lines · 84 tokens per session scan A af7d9fb95438
fix-ci is a skill published in the GitHub repository CliMA/ClimaAtmos.jl (126 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 4,852 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-30.
Other skills, from other repositories
fix-ci
Fix CI failures and performance regressions for a Julia package PR by iterating - triage the latest CI results, fix one root cause, verify locally, push. Use when a PR's GitHub Actions or Buildkite CI is failing, or when CI jobs run slower than they do on the main branch. Verifies CPU and GPU compilation locally…
fix-ci
Fix CI failures and performance regressions for a Julia package PR by iterating - triage the latest CI results, fix one root cause, verify locally, push. Use when a PR's GitHub Actions or Buildkite CI is failing, or when CI jobs run slower than they do on the main branch. Verifies CPU and GPU compilation locally…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
pysr
Use when fitting equations to data with PySR or SymbolicRegression.jl, when a user wants an interpretable formula, symbolic model, scaling law, or empirical relation discovered from numeric data, or when debugging a PySR search that is slow, stuck, or giving poor equations.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
github-ci-fix
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.