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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/ci-readout)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/ci-readout"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/ci-readout/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/yeaight7/agent-powerups/ci-readout"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/ci-readout.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.00471 |
| Opus 5 | $0.00005 | $0.00235 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
ci-readout 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 3d 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
CI Readout Generation
CRITICAL BEHAVIORAL RULES
You MUST follow these rules exactly. Violating any of them is a failure.
- Read-only analysis. Do NOT modify production code during this phase.
- Identify true failures. Focus on actual job failures, ignoring cancelled or skipped jobs unless relevant.
- Halt on error. If unable to fetch CI data, STOP and inform the user.
- Use local context. Utilize available logs and workspace context to diagnose issues.
- Never enter plan mode autonomously. Execute the analysis directly.
Analysis Process
Use the Task tool to generate the readout:
Task:
subagent_type: "general-purpose"
description: "Generate CI readout for $ARGUMENTS"
prompt: |
You are a CI pipeline expert. Generate a comprehensive readout of the recent CI runs.
Analyze the CI status for: $ARGUMENTS
## Core Requirements
1. **Run Status Summary**
- Overall pipeline status (Pass, Fail, Running)
- Duration and critical path bottlenecks
- Job breakdown (e.g., Lint, Test, Build)
2. **Failure Diagnosis**
- Identify exactly which jobs failed
- Extract the relevant error messages or stack traces
- Differentiate between flaky tests, infrastructure errors, and true code regressions
3. **Metrics**
- Test pass/fail counts
- Coverage changes (if available)
- Build size changes
## Quality Checklist
- Clear, executive-level summary at the top
- Actionable insights for each failure
- No generic guesses; base analysis strictly on logs
- Links or references to specific log lines
## Output Requirements
- A markdown formatted report
- Next steps for the developer to fix the build
Validation
After generating the readout:
- Ensure the summary accurately reflects the latest pipeline state.
- Verify that error traces are concise and relevant.
- Confirm actionable next steps are provided.
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.
- 3d ago First seen · 67 lines · 11 tokens per session scan A 3688ff08f1ae
ci-readout is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 471 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-14.
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…
optimize-workflow
Analyze and optimize GitHub Actions workflow for performance, cost, and best practices.
t800-fix
A command for making a narrow, predefined fix to existing agents, skills, commands, rules, or hooks. A fix-pack is a file listing the exact changes to make.
check-pipeline
Analyze CI/CD pipeline configuration for optimization opportunities.
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. Use when CI is red, PR checks fail, or after a push with --watch.
cpp-build
Fix C++ build errors, CMake issues, and linker problems incrementally. Invokes the cpp-build-resolver agent for minimal, surgical fixes.