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/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/fix-ci)<a href="https://agentmods.dev/commands/technicalpickles/pickled-claude-plugins/fix-ci"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/fix-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/commands/technicalpickles/pickled-claude-plugins/fix-ci"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/fix-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.00040 | $0.00679 |
| Opus 5.5 | $0.00016 | $0.00272 |
| Sonnet 5.5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
fix-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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix CI Failures
Iteratively fix a failing Buildkite CI run. This command resolves what to fix, then loads the ci-cd-tools:fixing-ci skill to drive the loop (verify locally → push → check → iterate).
Arguments
- URL (optional): Buildkite build URL to start with
- If no URL provided, infer from current branch / open PR
Step 1: Resolve the Input
Determine the build to fix using this priority order:
- URL argument provided → use it directly. The
bktide snapshottool parses any Buildkite URL. - No URL, current git branch has an open PR → resolve via
gh pr view --json number,headRefName, then find the latest failing build for that branch using thebuildkite:investigating-buildsskill's "Checking Current Branch/PR Status" workflow. - No URL, current branch but no PR → ask the user for either the build URL or the PR number.
- Detached HEAD or no clear branch → ask the user.
Once resolved, you have one of: build_url, pr number, or branch name.
Step 2: Optional Tracking Document
For complex or multi-day debugging sessions, offer to create a tracking document:
"Would you like me to create a tracking document for this CI fix session? Useful for multi-day debugging or handoff."
If yes, create docs/plans/ci-fix-<branch-slug>.md with this template:
# CI Fix Workflow: <branch-name>
## Session: <YYYY-MM-DD>
### Initial State
- Branch: `<branch-name>`
- PR: #<pr-number>
- Latest failing build: <build-number> (<N> failures - <brief description>)
---
## Iteration 1: <Title>
**Build:** <number> (<status>)
**Failures:** <count> (<pattern description>)
**Root cause:**
<1-2 sentences>
**Fix:**
<Code changes or commands>
**Verification:**
\`\`\`bash
<local verification commands>
\`\`\`
**Commit:** `<sha>` - "<message>"
**Next build:** <number>
---
## Summary of Issues Fixed
| Build | Issue | Root Cause | Fix |
|-------|-------|------------|-----|
| <num> | <issue> | <cause> | <fix> |
## Next Steps
- [ ] <remaining items if session ends before green>
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 · 84 lines · 40 tokens per session scan A 7546697d87a4
fix-ci is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (12 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 679 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 commands, from other repositories
health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage.
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
doctor
Check the Modellix CLI install, credential resolution, API connectivity, and balance.
duck-off
Turn off Rubber Duck mode and answer normally.
bug-report-triage
Turn a vague bug report into a structured, actionable ticket with severity and next steps.
azure-devops-orchestrator:pipeline
Pipeline monitoring and debugging: check recent runs, analyze failures, detect flaky tests, suggest fixes. Provides deep diagnostics for Azure DevOps pipeline issues.