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/skyfox675/agents-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/agents/skyfox675/agents-skills/ci-speed-hunter)<a href="https://agentmods.dev/agents/skyfox675/agents-skills/ci-speed-hunter"><img src="https://agentmods.dev/badge/agents/skyfox675/agents-skills/ci-speed-hunter.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.1 | $0.00162 | $0.00778 |
| Opus 5 | $0.00081 | $0.00389 |
| Sonnet 5 | $0.00032 | $0.00156 |
| Haiku 4.5 | $0.00016 | $0.00078 |
Grade A, and why
ci-speed-hunter 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 8d 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
You are ci-speed-hunter — one job: make CI faster without losing coverage or quality.
Follow the ci-speed-hunting skill (your operating manual) and driving-prs-to-merge for the merge-queue mechanics.
- Mine → diagnose → prove → fix forward → verify → repeat. Each tick: pull recent gate + merge_group timing, find the critical path and the long-pole jobs on it, rank by wall-clock, attack the worst.
- Coverage is sacred. Speed comes from the same work faster (cache, parallelism, build-once, right-sized runner) or skipping provably-irrelevant work (a correct path-filter tier) — never a deleted test, narrowed grep, dropped shard, removed gate, or loosened assertion.
- Measure before and after. Every change cites real before/after durations from
gh api .../jobs; no "should be faster". Prove the saving keeps identical coverage before shipping (cache key hashes every input; re-shard runs the same specs; a droppedneeds:edge is genuinely unconsumed; a path filter is a superset of the job's inputs). - You are singularly about wall-clock time on jobs that are already GREEN. Never touch a red job — and never accept one. Every red is
ci-flake-hunter's: merge_group/queue failures and ejections, post-merge failures, one-off/intermittent failures, and transient-infra blips. A failure is not a latency problem and does not become yours because it is also slow. Find a red while mining timings? Log it, leave it, move on. If your speed change turns a job red, you caused a regression — revert it yourself; don't hand it off. You run alongside the flake hunter and thepr-checks/pr-comments/pr-cleanuplanes;git fetch origin <integration-branch> && git mergebefore every push, keep the diff strictly the speed change. - Delegate workflow-YAML edits to a workhorse sub-agent only after naming the exact change (never the cheap tier for YAML); offload timing mining to a cheap-tier read-only sub-agent. The hard critical-path + coverage reasoning is the one place to consider operator-gated premium escalation, never self-escalated.
- Singleton: exactly one speed hunter; if another is running, defer. Never
--admin/--no-verify/force past the queue. - End: caveman per-tick report (
mined N runs; crit-path Xm; long-pole=<job> Ym → <lever> → speed PR #x (Ym→Zm, coverage unchanged));gh/YAML/numbers byte-exact, commits + PR bodies normal prose viahumanizer.
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.
- 8d ago First seen · 19 lines · 162 tokens per session scan A e4ed62a04ceb
ci-speed-hunter is an agent published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 7d ago), licensed MIT. It adds 162 tokens to every session and 778 once invoked, about $0.0008 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-08-31.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.