Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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.
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWrote 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/commands/rohitg00/awesome-claude-code-toolkit/analyze-ci-failure)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/analyze-ci-failure"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/analyze-ci-failure.svg" alt="Measured on agentmods" 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.00015 | $0.00375 |
| Opus 5 | $0.00008 | $0.00187 |
| Sonnet 5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
analyze-ci-failure 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 8d 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
/analyze-ci-failure - Analyze CI/CD Failure
Analyze and diagnose a CI/CD pipeline failure.
Steps
- Identify the CI/CD platform: GitHub Actions, GitLab CI, CircleCI, Jenkins, Azure DevOps
- Locate the failed pipeline run from logs, URL, or recent git push
- Retrieve the full build log output for the failed step
- Identify the exact failure point: which step, which command, which line
- Classify the failure type: build error, test failure, lint error, deployment error, infra issue
- Extract the error message and relevant stack trace
- Check if the failure is flaky by reviewing recent run history for the same job
- Analyze the error against common CI failure patterns:
- Dependency installation failures (network, version conflicts)
- Test timeouts or resource exhaustion
- Docker build failures (layer caching, missing base image)
- Permission or credential issues
- Check for environment differences between local and CI
- Suggest specific fixes with code changes or configuration updates
- If the fix requires a pipeline config change, show the exact diff
- Provide a confidence level for the diagnosis and suggested fix
Rules
- Focus on the root cause, not symptoms (a test timeout may be caused by a resource leak)
- Check for recent changes to the CI config file that may have introduced the failure
- Consider caching issues: suggest clearing cache if the error is inconsistent
- Check if the failure only occurs on CI (environment-specific issue)
- Look for secret or credential expiration as a common cause
- Do not expose secret values in the analysis output
- Suggest adding better error handling to prevent obscure failures
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.
- 8d ago First seen · 38 lines · 15 tokens per session scan A e3a6a6c00ae2
analyze-ci-failure is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,595 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 375 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.