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 me-cedric/agent-compass --skill ci-triagegit clone --depth 1 https://github.com/me-cedric/agent-compassWrote 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/me-cedric/agent-compass/ci-triage)<a href="https://agentmods.dev/skills/me-cedric/agent-compass/ci-triage"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/ci-triage/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/me-cedric/agent-compass/ci-triage"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/ci-triage.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.00000 | $0.00706 |
| Opus 5.5 | $0.00000 | $0.00282 |
| Sonnet 5.5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
ci-triage 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ci-triage
A red pipeline is not always a code defect. Read the failed job, not the pipeline color.
Steps
- Get the failed job log:
- GitHub:
gh run list --limit 5, thengh run view <run-id> --log-failed. - GitLab:
glab ci status, thenglab ci trace <job>.
- GitHub:
- Read the log from the first error, not from the last line.
- Note which jobs pass. If tests, lint and typecheck pass, suspect the environment or a gate that runs over the whole commit range.
- A commit linter runs over every commit of the branch. One inherited commit with a bad subject reddens each build. Reword or squash that commit. Do not change code.
- Classify the failure, using the table.
- Reproduce it locally with the command that the CI file runs, the same tool versions and a lockfile install.
- If you cannot reproduce it, say so. Name the likely difference: OS, env var, test order, time zone, network, cache.
- Make the smallest fix for one cause. Do not skip, weaken or delete a test. Do not relax a gate.
- Run the checks locally. Push only when the user asks.
- Rerun the failed job:
gh run rerun <run-id> --failed, orglab ci retry <job>. Confirm that it passes.
Classes
| Class | Sign | Action |
|---|---|---|
| Flaky | Passes on a rerun. The cause is timing, order or shared state. | Find the cause. Rerun once to confirm. Do not hide it with a retry. |
| Environment | The runner, network, cache, secret, quota or tool version failed. Unrelated commits fail the same way. | Fix the CI config or tell the owner. Do not change code. |
| Real | It fails on the same commit locally, and a change in the diff explains it. | Fix the code. |
Packaging builds
An exit code is not a build result for an installer, an image, an APK or a binary.
- The artifact exists at the path that the build declares.
- It comes from this run. Compare it with a marker file that you create when the run starts. Do not compare it with a source file time.
- It opens:
unzip -t,tar -tf,docker image inspect,hdiutil verify. - A zero exit can ship the previous build, because a bundler may reuse an existing output directory. Delete the output before the build.
- A non-zero exit can still leave a good artifact, because packaging runs last. Look before you call the build failed.
- Clean the leftover state at the start of each build, not after a failure.
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 Changed · -48 tokens per session 5799aab650ff
- 10d ago First seen · 50 lines · 48 tokens per session scan A 4949955d3346
ci-triage is a skill published in the GitHub repository me-cedric/agent-compass (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 706 tokens. 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-10-18.
Other skills, from other repositories
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
ci-troubleshoot
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to know which workflow does…
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
taste-lints
Use when you say run taste lints, check file size, or lint taste invariants. Custom lints with agent-readable remediation instructions for file size, naming conventions, structured logging, and complexity.