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/LeanAndMean/mach10Wrote 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/leanandmean/mach10/pr-ci-fix)<a href="https://agentmods.dev/commands/leanandmean/mach10/pr-ci-fix"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/pr-ci-fix/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/leanandmean/mach10/pr-ci-fix"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/pr-ci-fix.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.00011 | $0.00736 |
| Opus 5.5 | $0.00004 | $0.00294 |
| Sonnet 5.5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
pr-ci-fix 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix CI Failures
You are diagnosing and fixing failing CI checks on a pull request. This command fetches CI failure details from GitHub, then delegates to the feature-dev workflow for root cause analysis and implementation of fixes.
User input: $ARGUMENTS
Step 1: Parse Input
The user's input typically contains:
- A PR number (required)
- Additional context about which checks to focus on (optional)
Example inputs:
108108 only the linting failure108 ignore the coverage check, focus on the unit test failures
Extract the PR number. If the user provided context about which checks to focus on, note it for Step 3. If the input is ambiguous, ask the user to clarify.
Step 2: Checkout PR Branch
Ensure you are on the correct branch:
gh pr checkout <pr-number>
git pull
Step 3: Gather CI Failure Details
This is the key step -- fetch CI check status and failure logs.
List all checks:
gh pr checks <pr-number>
If all checks are passing, report this to the user and stop. Suggest re-running /mach10:pr-review <pr-number> or /mach10:pr-pre-merge <pr-number> as the next step instead.
For each failed check, get the run ID and fetch the failed logs:
gh run view <run-id> --log-failed
If the user provided context about which checks to focus on, filter to only the relevant failed checks. Otherwise, gather logs for all failed checks.
If the logs are very large, extract the most relevant sections:
- Test names and assertion failures
- Stack traces
- Error messages and exit codes
- The last ~100 lines of each failed step
Get PR context so the fix session understands what the PR is about:
gh pr view <pr-number>
Step 4: Delegate to Feature Dev
Use the Skill tool to invoke /feature-dev:feature-dev with the following context:
This PR (#) has failing CI checks. Here are the failure details:
<include the CI failure logs and error messages gathered in Step 3>
Perform a root cause analysis of these CI failures, then implement fixes using the 7-phase development plan. IMPORTANT: After reading the development plan phases, add each phase as a task to your todo list so you do not skip any phases.
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 · 90 lines · 11 tokens per session scan A 65c01eb382a9
pr-ci-fix is a command published in the GitHub repository LeanAndMean/mach10 (21 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 736 once invoked, about $0.0000 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 commands, from other repositories
ci
Diagnose and fix a red CI run — dispatches orc-ci-investigator, then routes on its verdict: auto-fix via orc-code-fixer, flake re-run, infra escalation, or /orc:debug hand-off.
crystallize
After a session or an incident, turn what happened into reusable knowledge — learn captures this session's lessons, review/approve promotes incident patterns into agent improvements, skill turns a repeating procedure into a skill.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
debug
Route a failure to the right debug methodology.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
debug
Diagnose a broken or misbehaving Deploio app. Triggers the deploio-debug skill — autonomously pulls logs, release history, and runtime stats, then identifies the root cause and proposes a fix.