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/allisoneer/agentic_auxilaryWrote 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/allisoneer/agentic_auxilary/resolve_pr_ci_failures)<a href="https://agentmods.dev/commands/allisoneer/agentic_auxilary/resolve_pr_ci_failures"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/resolve_pr_ci_failures/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/allisoneer/agentic_auxilary/resolve_pr_ci_failures"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/resolve_pr_ci_failures.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.00015 | $0.01210 |
| Opus 5 | $0.00008 | $0.00605 |
| Sonnet 5 | $0.00003 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
resolve_pr_ci_failures 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 yesterday.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Non-blocking bot-review or advisory checks should not block remediation unless they surface actionable failures.
Gather GitHub Actions failure evidence via Bash+gh, attempt only safe grounded remediation, verify any claimed fix, and write a durable artifact.
<workflow_contract>
- Follow all steps in order.
- Use
todowriteand keep exactly one todoin_progress. - Create the artifact early and keep updating it with evidence, decisions, actions, and verification.
- Treat v1 required CI as all visible non-skipped, non-neutral checks for the current PR head SHA, except clearly non-blocking bot-review or advisory signals.
- Use Bash+
ghfor raw CI evidence when current Rust/MCP GitHub surfaces are insufficient. - Attempt remediation only when the failure cause and the fix are both grounded and bounded.
- If remediation is unsafe, ambiguous, or inconclusive, stop with explicit handoff details in the artifact.
- Any claimed code/config fix must be verified with strong checks and at minimum
just checkandjust testunless impossible. </workflow_contract>
<step_1>
Step 1: Establish PR context and todo list
- Determine the current PR number, PR URL, branch, and head SHA.
- Create todos for: context capture, CI evidence collection, analysis, bounded remediation or handoff, verification, artifact finalization.
- Name the artifact with the PR number and head SHA when available.
</step_1>
<step_2>
Step 2: Capture initial CI state into an artifact
- Create a durable artifact under
thoughts/<branch>/artifacts/before making changes. - Record:
- PR metadata and head SHA
- invocation context
- current required-CI policy for this workflow
- Treat the artifact as the running source of truth for all later evidence and decisions.
</step_2>
<step_3>
Step 3: Gather grounded CI evidence with Bash + gh
In bounded Bash child work, gather best-effort evidence for the current PR head SHA:
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.
- yesterday First seen · 154 lines · 15 tokens per session scan A 47d7bd032bac
resolve_pr_ci_failures is a command published in the GitHub repository allisoneer/agentic_auxilary (77 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,210 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-09-08.
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.