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 mostafa-drz/claude-skills --skill investigate-cigit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/investigate-ci)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/investigate-ci"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/investigate-ci/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/mostafa-drz/claude-skills/investigate-ci"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/investigate-ci.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.00050 | $0.02065 |
| Opus 5.5 | $0.00020 | $0.00826 |
| Sonnet 5.5 | $0.00010 | $0.00413 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
investigate-ci 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 1mo 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate CI
Investigate GitHub Actions failures — fetch logs, diagnose root causes, suggest fixes.
Preferences
Read ~/.claude/skills/investigate-ci/preferences.md using the Read tool. If not found, no preferences are set.
Context
On startup, use Bash to detect: current repo (gh repo view --json nameWithOwner -q .nameWithOwner) and default org (gh repo view --json owner -q .owner.login). Skip any that fail.
Command Routing
Check $ARGUMENTS for subcommands:
help
If $ARGUMENTS is "help" (case-insensitive), display:
Investigate CI — diagnose GitHub Actions failures
Usage:
/investigate-ci <workflow-url> Investigate a specific workflow
/investigate-ci <run-url> Investigate a specific run
/investigate-ci <repo> [workflow] Investigate by repo name
/investigate-ci config Set preferences
/investigate-ci reset Clear preferences
/investigate-ci help This help
Examples:
/investigate-ci https://github.com/org/repo/actions/workflows/deploy.yml
/investigate-ci https://github.com/org/repo/actions/runs/12345678
/investigate-ci ai-stacks deploy.yml
/investigate-ci ai-stacks All failing workflows
/investigate-ci 12345678 Run ID (uses current/default repo)
Current preferences:
[show from preferences.md or "defaults"]
Then stop.
config
If $ARGUMENTS is "config" or "configure", use AskUserQuestion:
Question 1 — "Default organization?" (multiSelect: false)
- Detect from current repo
- Always ask
Question 2 — "How many recent runs to check?" (multiSelect: false)
- 5 (quick)
- 10 (default)
- 20 (thorough)
Question 3 — "Default branch filter?" (multiSelect: false)
- All branches (default)
- Main/prod only
- Current branch
Save to ~/.claude/skills/investigate-ci/preferences.md. Display summary. Then stop.
reset
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.
- 1mo ago Changed · +3 lines 5a35657e7d30
- 1mo ago First seen · 239 lines · 50 tokens per session scan A f38bdf79bd42
investigate-ci is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 2,065 once invoked, about $0.0002 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
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks", "update megalinter skills". Always goes through npx mega-linter-runner…
rudder-destination-debugging
Diagnoses why events are failing, dropping, or not arriving at a destination. Use when events are missing from a destination, seeing high error rates, getting auth failures, or events are stuck retrying.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
gh-fix-ci
Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose a plan, and only implement after explicit user approval. External CI providers (Buildkite, CircleCI, etc.) are reported by URL only.
investigating-builds
Use when the user is working with an existing Buildkite CI run and wants to understand, diagnose, or act on it. Strong signals: a buildkite.com URL, the word "buildkite", the bk CLI, the bktide tool, or a reference to a specific pipeline, build, or job. Covers intents like: "why did this build fail", "what's flaking"…
rudder-profiles-debug
Diagnoses RudderStack Profiles compile failures, run failures, and output-quality problems. Use when pb compile fails, pb run fails, identity stitching looks wrong, output quality regresses, or Profiles errors need structured recovery.