Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/whiteboard/main/.claude/skills/ci-triage/SKILL.mdgit clone --depth 1 https://github.com/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/ci-triage)<a href="https://agentmods.dev/skills/kamiazya/whiteboard/ci-triage"><img src="https://agentmods.dev/badge/skills/kamiazya/whiteboard/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/kamiazya/whiteboard/ci-triage"><img src="https://agentmods.dev/badge/skills/kamiazya/whiteboard/ci-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00106 | $0.02776 |
| Opus 5 | $0.00053 | $0.01388 |
| Sonnet 5 | $0.00021 | $0.00555 |
| Haiku 4.5 | $0.00011 | $0.00278 |
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 6d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI & automated-review triage (whiteboard)
lefthook (pre-push) catches local build/test/typecheck breakage before push. This skill covers the layer ONLY the cloud sees after push: CI workflows + the GitHub-App review bots on the PR. The integrator monitors them, separates signal from noise, and files actionable items into the Task list / tmp/issues (or fixes quick ones on the spot).
What runs on this repo (verified surface)
| Source | What it is | How to read it |
|---|---|---|
verify |
GitHub Actions CI (lint:noconsole + tests/typecheck/smoke per .github/workflows/) |
gh pr checks <PR>; logs: gh run view <run-id> --log-failed |
| CodeRabbit | AI PR review (line comments + summary). Skips while the PR title contains WIP/draft |
gh pr view <PR> --json reviews,comments; gh api repos/{owner}/{repo}/pulls/<PR>/comments |
| AccessLint | accessibility review app | its check + PR review comments |
| WIP | reports work-in-progress from the title — informational, measured not to block a merge (#1201: with WIP the sole non-success check, mergeable_state read unstable, never blocked; Draft is the one mechanical merge block) |
gh pr checks shows it pending; remove WIP/(WIP) from the title to settle it + un-skip CodeRabbit |
| CodeQL | security code-scanning | primary (scope-free): its findings post as PR review comments by github-advanced-security[bot] — gh api repos/{owner}/{repo}/pulls/<PR>/comments --jq '.[]|select(.user.login=="github-advanced-security[bot]")'. enrichment (may 404 on scope / "no analysis"): gh api repos/{owner}/{repo}/code-scanning/alerts (needs security_events/admin) for severity/state |
| Dependabot | dependency-bump PRs + security alerts | handled by its own flow — the dependabot-triage workflow + dependabot-review skill (semver×ecosystem classify, conflict-cascade-safe merge, pnpm audit --prod gate). Don't triage it here. |
Note: some security APIs need gh auth refresh -s security_events (or admin) — if a fetch 404s on scope, skip that source and note it rather than failing the triage.
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.
- 6d ago Changed · +42 lines f881b1bdc345
- 7d ago Changed 7bf883766839
- 10d ago First seen · 90 lines · 106 tokens per session scan A 4e642bf4b926
ci-triage is a skill published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 106 tokens to every session and 2,776 once invoked, about $0.0005 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
gemini-review
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration.
squid-implement-night
Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
review
Review before merge. Stage-1 spec-compliance gate, then risk-selected Stage-2 review axes from the canonical set. analyst always runs, callers can pin extra always-on axes, and explicit deep review runs the full 16-axis set. Run after /test. Do NOT invoke code-qualities-assessment, doc-accuracy, golden-principles, or…