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.
npx skills add juan294/cc-rpi --skill source-command-fix-cigit clone --depth 1 https://github.com/juan294/cc-rpiWrote 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/skills/juan294/cc-rpi/source-command-fix-ci)<a href="https://agentmods.dev/skills/juan294/cc-rpi/source-command-fix-ci"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/source-command-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/skills/juan294/cc-rpi/source-command-fix-ci"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/source-command-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.00014 | $0.00499 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
source-command-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 5d 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
source-command-fix-ci
Use this skill when the user asks to run the migrated source command fix-ci.
Command Template
Self-healing CI: diagnose and fix all failing tests autonomously.
Model tier: sonnet — Sonnet 5 (1M context) session. All subagents: model: "sonnet".
Process:
-
Get the latest CI run for the current branch:
gh run list --branch $(git branch --show-current) --limit 1 --json databaseId,conclusion,statusIf CI is green or still running, report status and stop. -
Get the failure logs:
gh run view <run-id> --log-failed 2>&1 | tail -200 -
Parse failures into individual test/check failures. Group by:
- Type errors (typecheck)
- Lint errors
- Test failures (list each failing test)
- Build failures
-
For each failing test, spawn a sub-agent (model:
"sonnet") to: a. Read the failing test file and the source file it covers b. Identify the root cause from the error message c. Fix the SOURCE code (never weaken or delete a test) d. Verify that specific test passes locally -
For typecheck/lint/build failures, fix them directly (these are usually straightforward).
-
After all fixes, run the full test suite locally:
pnpm run typecheck 2>&1; pnpm run lint 2>&1; pnpm run test 2>&1 -
If new failures appear, repeat the fix cycle (max 3 iterations).
-
When all checks pass, commit with message:
fix: resolve CI failures [auto]Then push and spawn a background agent to verify CI passes.
Rules:
- Never weaken a test to make it pass — fix the source code.
- Never delete a test.
- If a failure is flaky (passes locally, fails in CI), note it but don't skip.
- If stuck after 3 fix cycles, stop and report what remains broken.
- Verify the current branch before committing.
- Normal CI repair happens on the branch under test.
Never push directly to
mainwithout explicit approval.
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.
- 5d ago First seen · 56 lines · 14 tokens per session scan A d03b378e3601
source-command-fix-ci is a skill published in the GitHub repository juan294/cc-rpi (5 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 499 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-06.
Other skills, from other repositories
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.
playwright-ci-caching
Cache Playwright browser binaries in CI/CD pipelines (GitHub Actions, Azure DevOps) to avoid 1-2 minute download overhead on every build.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.