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 mblode/agent-skills --skill ci-speedupgit clone --depth 1 https://github.com/mblode/agent-skillsWrote 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/mblode/agent-skills/ci-speedup)<a href="https://agentmods.dev/skills/mblode/agent-skills/ci-speedup"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/ci-speedup/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/mblode/agent-skills/ci-speedup"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/ci-speedup.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.00083 | $0.02195 |
| Opus 5.5 | $0.00033 | $0.00878 |
| Sonnet 5.5 | $0.00017 | $0.00439 |
| Haiku 4.5 | $0.00008 | $0.00219 |
Grade A, and why
ci-speedup 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Speedup
Make the wait from push to green shorter, measured, and written down.
- IS: measuring a pipeline's critical path from run timestamps, choosing the levers that shorten it, changing workflow and test configuration, and recording before and after with the trend that says when the next round is due.
- IS NOT: getting a red build green (
pr-babysitter), writing a pipeline for a package that has none (scaffold-cli), deleting low-value tests (test-audit), or general repository hygiene.
What Changes the Number
Wall-clock is the slowest chain of dependent jobs, not their sum. The number is push to green for one pull request, median and p90 over recent runs. Around five minutes an agent loop stops waiting on checks and the bottleneck moves to deploy and review. A lever that saves runner minutes off the critical path is a cost saving, and the ledger records it as one.
Three ratios decide what to do next:
- Setup tax. Checkout, runtime, dependencies, and service boot, per job. 110 seconds of setup around 60 of work is a batching candidate; around 400 it is a sharding candidate. Each shard adds a setup, so cut setup before adding shards.
- Import versus test. When Vitest's import plus environment figures exceed its tests figure, the suite pays to boot the module graph per file. A shared registry or a lighter environment moves that; more shards only spread it.
- Gate versus work. Change detection, matrix computation, and cache saves sit on the chain. Anything they do beyond deciding is paid by every job behind them.
Reference Files
| File | Read when |
|---|---|
references/measuring.md |
Step 1: run, job, and step timings; percentiles; the critical path; test-runner duration lines; the baseline table. Step 4: the rules that decide whether the after-run credits a lever |
references/levers.md |
Step 2: the lever catalogue by class, what each needs to be true, expected gain, how each has failed |
references/ledger.md |
Step 5: the ledger, its trend table, and the instruction-file lines that stop the layout regressing |
scripts/ci-timings.sh |
Step 1: one run's jobs, steps and critical path, or --runs N for median and p90 per job; --help gives the forms |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 39e85963748a
- 5d ago Changed · -4 lines · -21 tokens per session 373626a6a9b2
- 15d ago Changed 903b7052acb2
- 17d ago Changed 60b6840992ad
- 18d ago First seen · 99 lines · 104 tokens per session scan A b58102466493
ci-speedup is a skill published in the GitHub repository mblode/agent-skills (144 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 2,195 once invoked, about $0.0003 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-09-22.
Other skills, from other repositories
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.
handoff
Finish a vibe session in symphony-alpha and hand it to whoever picks it up next, usually design and then engineering. Through workers, completes internal scope and Storybook checks, writes focused tests at handoff, runs lint, typecheck and tests, reviews the integrated result and fixes confirmed findings. Asks who…
build-status-cache
Skip Phase 7 rebuild when no code changed since Phase 5 build passed. Compares git diff hash against stored hash from last successful build validation. Triggers on: entering Phase 7, checking build status, before final build validation. Returns BUILDCACHEHIT to skip or BUILDCACHEMISS to re-run build-validator.
auto-optimize
Autonomously optimize an existing skill's output quality by running it repeatedly, scoring against binary evals, mutating the prompt, and keeping improvements. Started only by the user, because it edits the skill in place and runs many paid model calls.
guided-manual-qa
Derive and run an interactive, evidence-recorded manual QA session for a code change, ticket, branch, or pull request. Use when a human should validate live behavior checkpoint by checkpoint after repository-aware setup; do not use as a substitute for automated tests or a read-only code review.
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.