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 agentmods add skills/pymodel/pythinker-cli/diagnose-ci-failuresnpx skills add PyModel/pythinker-cli --skill diagnose-ci-failuresgit clone --depth 1 https://github.com/PyModel/pythinker-cliWhat 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 | $0.00031 | $0.00236 |
| Opus 5 | $0.00015 | $0.00118 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
diagnose-ci-failures 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 2d 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
Diagnose CI Failures
Use when a CI job, local test, lint, typecheck, or build gate fails.
Workflow
- Capture the failing command, exit code, and the first actionable error.
- Identify whether the failure is deterministic, flaky, environmental, or caused by recent code.
- Reproduce with the narrowest local command when practical.
- Name the root cause before editing.
- Make the smallest fix that addresses the root cause.
- Rerun the focused failing gate and report the result.
Rules
- Do not skip hooks or weaken tests to make CI pass.
- Do not hide unrelated failures; separate them from the fixed failure.
- Prefer targeted tests over full-suite runs until the focused failure is fixed.
- If a gate cannot run because of missing tools or credentials, report that clearly.
Output
Return:
SUMMARY
ROOT CAUSE
CHANGES
VERIFICATION
REMAINING RISKS
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.
- 2d ago First seen · 37 lines · 31 tokens per session scan A 5773c47e03ae
diagnose-ci-failures is a skill published in the GitHub repository PyModel/pythinker-cli (20 stars, last pushed 5d ago), licensed Apache-2.0. It adds 31 tokens to every session and 236 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ci
A specialized skill for Gemini CLI that provides high-performance, fail-fast monitoring of GitHub Actions workflows and automated local verification of CI failures. It handles run discovery automatically—simply provide the branch name.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
playwright-devops
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
fixing-streamlit-ci
Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally.
triage-ci-flake
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…