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 PyModel/pythinker-cli --skill diagnose-ci-failuresgit clone --depth 1 https://github.com/PyModel/pythinker-cliWrote 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/pymodel/pythinker-cli/diagnose-ci-failures)<a href="https://agentmods.dev/skills/pymodel/pythinker-cli/diagnose-ci-failures"><img src="https://agentmods.dev/badge/skills/pymodel/pythinker-cli/diagnose-ci-failures/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/pymodel/pythinker-cli/diagnose-ci-failures"><img src="https://agentmods.dev/badge/skills/pymodel/pythinker-cli/diagnose-ci-failures.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.00031 | $0.00236 |
| Opus 5.5 | $0.00012 | $0.00094 |
| Sonnet 5.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 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.
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.
- 1mo 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 (21 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 236 once invoked, about $0.0001 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
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
atmos-lint
Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
audit
Fast quality gate — detects stack, runs static analysis, checks cross-layer consistency, fixes issues. Run between every pipeline phase, before every commit push, after every feature batch. Lighter than /analyze but catches the same critical issues.
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.