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 BlackBeltTechnology/pi-agent-dashboard --skill ci-troubleshootgit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/ci-troubleshoot)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/ci-troubleshoot"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/ci-troubleshoot/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/blackbelttechnology/pi-agent-dashboard/ci-troubleshoot"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/ci-troubleshoot.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.00097 | $0.04336 |
| Opus 5.5 | $0.00039 | $0.01734 |
| Sonnet 5.5 | $0.00019 | $0.00867 |
| Haiku 4.5 | $0.00010 | $0.00434 |
Grade A, and why
ci-troubleshoot 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Troubleshoot
Diagnose CI failures for pi-agent-dashboard. The repo has 11 workflow files: 9 entry workflows and 2 reusable workflows.
flowchart LR
ci[ci.yml] --> checks[guards + lint + build<br/>+ affected tests]
nightlyTests[nightly-tests.yml] --> full[full suite + nightly-tests issue]
deploy[deploy-site.yml] --> pages[GitHub Pages]
native[ci-e2e-electron.yml] --> nativeTests[native Electron E2E]
ciSmoke[ci-smoke.yml] --> smoke[_smoke.yml]
publish[publish.yml] --> smoke
ciElectron[ci-electron.yml] --> electron[_electron-build.yml]
nightly[nightly.yml] --> electron
publish --> electron
publish --> release[GitHub Release]
release --> sync[sync-release-version.yml]
Full per-workflow detail: references/workflow-taxonomy.md.
First moves — always run these
pnpm exec tsx .pi/skills/ci-troubleshoot/scripts/list-recent-runs.ts # last 10 runs across all workflows
pnpm exec tsx .pi/skills/ci-troubleshoot/scripts/list-recent-runs.ts --failed # only failed
pnpm exec tsx .pi/skills/ci-troubleshoot/scripts/show-failed-run.ts <run-id> # failed steps + log tails
pnpm exec tsx .pi/skills/ci-troubleshoot/scripts/show-failed-run.ts # most recent failed run
These wrap gh run list, gh run view --log-failed, and similar. You need gh auth status to be authenticated.
ci.yml job taxonomy — affected-only tests
ci.yml runs parallel jobs (change: speed-up-ci-affected-tests):
| Job | Does | Red means |
|---|---|---|
select |
scripts/select-affected-tests.mjs → artifact test-selection + job summary |
selector could not run at all (it degrades to mode: full on its own errors) |
ci |
guards, spec validate, lint, lint:e2e, Biome, build, publish-import checks — NO tests |
a guard/lint/build failure |
unit ×4 |
the selector's shard n via pnpm run test:parallel <files> |
a test failed, dist/index.html missing, or verify-executed found an assigned file that never ran |
real-process |
real-process files (runs only when selected) | as today's phase 2; retries once under CI |
ci-scenarios |
the RUN_CI_SCENARIOS-gated packaging files only (skipped for OpenSpec-only diffs) |
a packaging scenario failed |
ci-result |
aggregate; check-result.mjs |
select failed, a job failed/cancelled, or an EXPECTED job was skipped |
What ships with it
12 files 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.
- references/common-failures.md 7.2 KB
- references/common-failures.md.AGENTS.md 342 B
- references/release-pipeline.md 5.6 KB
- references/release-pipeline.md.AGENTS.md 343 B
- references/workflow-taxonomy.md 3.1 KB
- references/workflow-taxonomy.md.AGENTS.md 257 B
- scripts/list-recent-runs.ts 2.4 KB runs code
- scripts/retrigger-failed.ts 2.6 KB runs code
- scripts/retrigger-failed.ts.AGENTS.md 277 B
- scripts/show-failed-run.ts 2.4 KB runs code
- SKILL.agent.md 6.8 KB
- SKILL.md.AGENTS.md 320 B
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 403a2b5f4169
- 15d ago Changed · +20 lines 9df6194b971a
- 25d ago Changed · +36 lines · +4 tokens per session a90adcee11a8
- 1mo ago Changed · +29 lines 15961c83a560
- 1mo ago First seen · 138 lines · 93 tokens per session scan A 076ccf426fb4
ci-troubleshoot is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (332 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 4,336 once invoked, about $0.0004 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-30.
Other skills, from other repositories
goga-prototype-plan-verification
Verification of the assembled architecture plan against the DSL.
goga-change-investigator
Evidence-driven root cause investigation.
goga-change-tracer
Semantic behavior reconstruction via tracing.
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
starfleet-github
GitHub PR/CI/backport interaction via starfleetctl (read-only + mutating commands, PR claims, backports). Load when checking PR status/CI, claiming a PR branch, submitting or repairing a PR, or backporting.
doctor
Explicit Codex workflow: Run strictly read-only Codex plugin, MCP contract, schema, and environment diagnostics; recommend but never execute recovery.