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.
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/fix-pipelinegit 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/fix-pipeline)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/fix-pipeline"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/fix-pipeline.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.00014 | $0.00319 |
| Opus 5 | $0.00007 | $0.00160 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
fix-pipeline 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 6d 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
/fix-pipeline - Fix CI/CD Pipeline
Apply fixes to a broken CI/CD pipeline configuration.
Steps
- Read the CI/CD configuration file (.github/workflows/*.yml, .gitlab-ci.yml, etc.)
- Identify the failing step and its configuration
- Determine the fix based on the failure analysis
- For dependency issues: update versions, add caching, fix lock files
- For test failures: increase timeouts, add retry logic, fix test environment
- For Docker issues: fix Dockerfile, update base images, fix build context
- For credential issues: verify secret names, check expiration, update references
- Apply the configuration fix to the pipeline file
- Add or update caching configuration to speed up future builds
- Add failure notification steps if not already present
- Run a dry-run or validation of the pipeline config if the platform supports it
- Commit the fix and report what was changed and why
Rules
- Make minimal changes to fix the issue; do not refactor the entire pipeline
- Always validate the pipeline config syntax before committing
- Add comments explaining non-obvious configuration choices
- Do not change test expectations to make them pass; fix the underlying issue
- Preserve existing caching strategies unless they are causing the failure
- Keep pipeline execution time in mind; do not add expensive steps unnecessarily
- Test the fix on a feature branch before merging to main
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.
- 6d ago First seen · 34 lines · 14 tokens per session scan A d7cfae64fdca
fix-pipeline is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,591 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 319 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
ci
Analyze Github Actions logs and fix issues.
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.