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 agentmods add skills/juan294/cc-rpi/ci-workflownpx skills add juan294/cc-rpi --skill ci-workflowgit 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/ci-workflow)<a href="https://agentmods.dev/skills/juan294/cc-rpi/ci-workflow"><img src="https://agentmods.dev/badge/skills/juan294/cc-rpi/ci-workflow.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 | $0.00021 | $0.00801 |
| Opus 5 | $0.00010 | $0.00400 |
| Sonnet 5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
ci-workflow scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
## Buffer Output from execSync/spawnSync How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Workflow
Push Accountability
Use the branch that is currently under CI verification. In a
develop/main topology this is often develop. In a main-only repo
it is usually the temporary branch or PR branch being validated before
merge.
Wrong -- push and move on:
git push origin <branch-under-test>
# Start next task immediately, never check CI
Right -- spawn background agent to monitor CI:
git push origin <branch-under-test>
# Background agent:
gh run list --branch <branch-under-test> --limit 1
# If CI fails: investigate with gh run view <id> --log-failed
# Fix and re-push. The push isn't done until CI is green.
Buffer Output from execSync/spawnSync
Wrong -- .trim() fails because these return a Buffer by default:
const sha = execSync('git rev-parse HEAD').trim(); // TypeError
Right -- pass encoding explicitly:
const sha = execSync('git rev-parse HEAD', { encoding: 'utf-8' }).trim();
Running ESM CLI Tools
Wrong -- node <file> on a shebang + ESM script throws SyntaxError:
node ./bin/cli.js
Right -- run it as an executable, or use npx:
chmod +x ./bin/cli.js && ./bin/cli.js
npx .
Missing Dependencies
Wrong -- run commands in a worktree, fresh clone, or CI with no node_modules:
pnpm run build # Cannot find module ...
Right -- install first:
pnpm install && pnpm run build
Scaffolding Requires an Empty Directory
Wrong -- add config files before scaffolding, so the tool aborts:
echo "# Project" > CLAUDE.md
npx create-next-app@latest . # aborts: directory not empty
Right -- scaffold first, add config files after:
npx create-next-app@latest .
echo "# Project" > CLAUDE.md
Verification Command Sequencing
Wrong -- run typecheck, lint, test as parallel tool calls:
# Parallel call 1: pnpm run typecheck
# Parallel call 2: pnpm run lint
# Parallel call 3: pnpm run test
# If one fails, all parallel calls are killed (Error #1)
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 · 141 lines · 21 tokens per session scan A 3e86090279ee
ci-workflow is a skill published in the GitHub repository juan294/cc-rpi (5 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 801 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
ci-workflow-guide
Guide to SGLang CI workflow orchestration — stage ordering, fast-fail, gating, partitioning, execution modes, and debugging CI failures. Use when modifying CI workflows, adding stages, debugging CI pipeline issues, or understanding how tests are dispatched and gated across stages.
babysit-pr-to-pass-ci
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head. Use when asked to monitor, babysit, retry, or fix PR CI for lint.yml, pr-test.yml, pr-test-extra.yml, AMD, or other named workflows; classify failures as PR-related versus flaky or…
sglang-bisect-ci-regression
Investigate consistently failing SGLang CI tests by extracting the failure signature from scheduled or rerun workflows, bisecting the passing/failing commit window, checking runner or hardware specificity, and optionally reproducing on a remote GPU host.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.