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 guorunjie/skillpack-forge --skill ci-triage-demo-ci-triagegit clone --depth 1 https://github.com/guorunjie/skillpack-forgeWrote 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/guorunjie/skillpack-forge/ci-triage-demo-ci-triage)<a href="https://agentmods.dev/skills/guorunjie/skillpack-forge/ci-triage-demo-ci-triage"><img src="https://agentmods.dev/badge/skills/guorunjie/skillpack-forge/ci-triage-demo-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/guorunjie/skillpack-forge/ci-triage-demo-ci-triage"><img src="https://agentmods.dev/badge/skills/guorunjie/skillpack-forge/ci-triage-demo-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.00024 | $0.00251 |
| Opus 5 | $0.00012 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
ci-triage-demo-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 12d 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-demo-ci-triage
Generated from skillpack.yaml by Skillpack Forge.
Project
CI triage workflows for inspecting failing runs, isolating causes, and documenting flaky versus real failures.
Workflow
- Identify the failing workflow, job, commit, and relevant changed files
- Read the failed step logs before changing code or rerunning CI
- Map the failure to the narrowest local command, test, or package script
- Classify the failure as likely flaky, environment-related, or a real regression
- Apply the smallest fix or rerun decision, then document verification and remaining risk
Commands
- install:
npm install - test:
npm test - lint:
npm run lint - ci:failed:
npm run ci:failed
Principles
- Read failing logs and changed files before rerunning jobs
- Reproduce the smallest failing command locally when possible
- Separate flaky infrastructure failures from real regressions with evidence
- Record the failing job, suspected cause, rerun decision, and final verification
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.
- 12d ago First seen · 31 lines · 24 tokens per session scan A 5a28f7c28b08
ci-triage-demo-ci-triage is a skill published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 251 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-31.
Other skills, from other repositories
investigate-ci
Investigates GitHub Actions workflow failures for any repo. Fetches recent runs, identifies failures, extracts error logs, diagnoses root causes, and suggests fixes. Use when a deploy or CI workflow fails and you need to understand why.
mk:fix
Diagnoses and fixes bugs, type errors, lint failures, CI/CD issues, and runtime errors via root-cause-first investigation. Use for defect remediation. NOT for investigation without a fix (see mk:investigate); NOT for build-only compilation errors (see mk:build-fix).
atmos-lint
Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.