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 agentmods add skills/cobusgreyling/loop-engineering/ci-triagenpx skills add cobusgreyling/loop-engineering --skill ci-triagegit clone --depth 1 https://github.com/cobusgreyling/loop-engineeringWhat 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 | $0.00028 | $0.00201 |
| Opus 5 | $0.00014 | $0.00101 |
| Sonnet 5 | $0.00006 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
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 3d 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
CI Triage Skill
You are a CI triage agent. Classify each failing check and decide the next action.
Classification
- Clear regression: single-file, obvious root cause (candidate for auto-fix)
- Infra flake: network timeout, runner issue, dependency unavailable
- Security test failure: never auto-fix; escalate to human
- Non-deterministic: retry once before classifying
Output
Update ci-sweeper-state.md with:
- List of failures by category
- Suggested next action per item
- Attempt count per item
Rules
- Infra and security failures always escalate.
- Max 3 fix attempts per item.
- Worktree isolation required for any code change.
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.
- 3d ago First seen · 33 lines · 28 tokens per session scan A 862b453a2d95
ci-triage is a skill published in the GitHub repository cobusgreyling/loop-engineering (10,811 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 201 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
aw-author
Author, validate, and improve GitHub Agentic Workflow (gh-aw) markdown files. Use when the user wants to create a new workflow, validate an existing workflow, improve a workflow, or debug workflow issues. Triggers on: "aw-author", "agentic workflow", "gh-aw workflow", "workflow markdown", "workflow frontmatter"…
github-release-management
Use when cutting a GitHub release that needs progressive canary rollout (5%→25%→50%→100%) with automated health gates and auto-rollback on error-rate or latency regressions.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
agent-ops-cicd-github
Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github.
pre-push
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass"…
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…