Borrowing it
Nothing to install: this file belongs to Parslee-ai/neo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Parslee-ai/neo/main/.claude/commands/fix-ci.mdgit clone --depth 1 https://github.com/Parslee-ai/neoWrote 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/parslee-ai/neo/fix-ci)<a href="https://agentmods.dev/commands/parslee-ai/neo/fix-ci"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/fix-ci.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.00017 | $0.00348 |
| Opus 5 | $0.00009 | $0.00174 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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 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
Fix CI Failures
Analyze and fix CI check failures on a pull request.
Workflow
Step 1: Get CI Check Failures
Use @sentinel to fetch CI failure details:
- Run
gh pr checks $PR_URL --json name,state,bucket,link,description - For each failed check (bucket="fail"), get details
- If available, fetch failure logs from the check link
Step 2: Analyze Failures
Categorize the failures:
- Test failures: Which tests failed and why
- Build errors: Compilation or bundling issues
- Lint errors: Code style or static analysis issues
- Other: Deployment, security scans, etc.
Step 3: Generate Fix Plan
Create a focused fix plan:
- List each failure with its cause
- Propose specific code fixes
- Prioritize by severity
Step 4: Call /implement
Pass the fix plan to /implement to apply the fixes.
Final Output (STRICT JSON)
{
"fixed": true|false,
"failures_found": ["check-name-1", "check-name-2"],
"fixes_applied": ["description of fix 1", "description of fix 2"],
"summary": "Brief summary of what was fixed or why it couldn't be fixed"
}
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 · 55 lines · 17 tokens per session scan A fe3b6e936709
fix-ci is a command published in the GitHub repository Parslee-ai/neo (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 348 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-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
metrics
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
proxy-logs
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
traces
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
add-debug-wait
Add a wait step to a CI workflow for debugging test failures.
ci-fix
Fix CI pipeline issues with interactive approval.