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.
git 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/rules/guorunjie/skillpack-forge/ci-triage-demo)<a href="https://agentmods.dev/rules/guorunjie/skillpack-forge/ci-triage-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/ci-triage-demo.svg" alt="Measured on agentmods" 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.00157 | $0.00157 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
ci-triage-demo 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.
What it actually says
ci-triage-demo
Generated from skillpack.yaml by Skillpack Forge.
CI triage workflows for inspecting failing runs, isolating causes, and documenting flaky versus real failures.
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
Commands
- install:
npm install - test:
npm test - lint:
npm run lint - ci:failed:
npm run ci:failed
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 · 25 lines · 157 tokens per session scan A 8a9e9e6fd148
ci-triage-demo is a cursor rule published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 3mo ago), licensed MIT. It adds 157 tokens to every session, about $0.0008 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 cursor rules, from other repositories
ci
GitLab CI/CD pipeline review and scaffolding for Terraform and Helm/EKS deployments, including individual stages, jobs, manual gates on prod stages, and pipeline credentials. Use when user says 'review my pipeline', 'check my gitlab-ci', 'scaffold a pipeline', 'is my CI correct', 'is my pipeline gated before prod'…
github-actions
GitHub Actions workflow review, scaffolding, and security hardening. Use when user says 'review my workflow', 'check my actions', 'scaffold a workflow', 'is my CI correct', 'pin actions', 'OIDC to AWS', or when working in .github/workflows/.yml files.
debugging
Apply when diagnosing a bug, reproducing a failure, or performing root cause analysis. Covers systematic isolation, binary search, logging strategy, and hypothesis-driven investigation.
shell-scripting
Apply when writing or reviewing Bash or POSIX shell scripts — automation, CI steps, deploy scripts, or any shell-based tooling.
fixing-github-actions-builds
When the Github Actions build is broken.
xiigen-systematic-debugging
Make debugging reproducible and disciplined. Use for unclear failures, regressions, or unstable behavior.