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 coo1white/cool-workflow --skill ci-triagegit clone --depth 1 https://github.com/coo1white/cool-workflowWrote 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/coo1white/cool-workflow/ci-triage)<a href="https://agentmods.dev/skills/coo1white/cool-workflow/ci-triage"><img src="https://agentmods.dev/badge/skills/coo1white/cool-workflow/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/coo1white/cool-workflow/ci-triage"><img src="https://agentmods.dev/badge/skills/coo1white/cool-workflow/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.00066 | $0.00349 |
| Opus 5.5 | $0.00026 | $0.00140 |
| Sonnet 5.5 | $0.00013 | $0.00070 |
| Haiku 4.5 | $0.00007 | $0.00035 |
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 5d 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
Overview
Triage the failure before editing. Keep stdout/log evidence separate from diagnosis, identify the first failing command, and end with one verifier command that proves the proposed fix.
Workflow
- Capture the failing command, exit code, and the earliest meaningful error.
- Classify the failure as code, test expectation, generated artifact drift, environment, timeout, or external service.
- Inspect only the files needed to explain that first failure.
- Propose or implement the smallest fix.
- Run the narrow verifier first, then the full gate when the fix is plausible.
- Write the lesson back to
AGENTS.md's Build Memory section, an eval case, or the matching workflow skill when the failure pattern is likely to recur.
Commands
npm run build
npm test
npm run gen:manifests -- --check
npm run index:check
git diff --check
Use smoke tests directly for narrow verification:
node test/<name>-smoke.mjs
Output Rules
- Lead with the failing command and root cause.
- Quote only the shortest relevant log lines.
- Separate "confirmed" from "inference".
- Include the verifier commands actually run or still required.
What ships with it
1 file 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.
- 5d ago Changed 8adfb90c04cd
- 1mo ago First seen · 51 lines · 66 tokens per session scan A b575b6d5aca9
ci-triage is a skill published in the GitHub repository coo1white/cool-workflow (2 stars, last pushed 2d ago), licensed BSD-2-Clause. It adds 66 tokens to every session and 349 once invoked, about $0.0003 per session on Opus 5.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
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
agent-starters
Verify every starter supported by the stable production NVIDIA Elements CLI from a fresh consumer environment, investigate failures, and prepare at most one focused repair pull request. Use for nightly or scheduled production starter verification and starter availability failures.
agent-inspect
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents. Use when capturing framework-faithful traces, asserting TraceContract/TraceFacts, packaging Evidence v2, or inspecting local runs over read-only MCP (gettracefacts).
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…