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/queelius/claude-anvilWrote 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/queelius/claude-anvil/repo-sprint)<a href="https://agentmods.dev/commands/queelius/claude-anvil/repo-sprint"><img src="https://agentmods.dev/badge/commands/queelius/claude-anvil/repo-sprint/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/queelius/claude-anvil/repo-sprint"><img src="https://agentmods.dev/badge/commands/queelius/claude-anvil/repo-sprint.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.00027 | $0.00959 |
| Opus 5.5 | $0.00011 | $0.00384 |
| Sonnet 5.5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
repo-sprint 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo-sprint
"What's open right now?" Pulls together the signals that matter at the start of a coding day so you can pick the next thing to work on.
Workflow
Run the following queries in parallel and synthesize. Use mcp__repoindex__run_sql for each.
1. Dirty working trees
SELECT name, path, language FROM repos
WHERE is_clean = 0
ORDER BY name
2. Unpushed commits
SELECT name, ahead, path FROM repos
WHERE ahead > 0
ORDER BY ahead DESC
3. Recent commit activity (last 3 days)
SELECT r.name, r.language, COUNT(*) AS commits, MAX(e.timestamp) AS last
FROM events e JOIN repos r ON e.repo_id = r.id
WHERE e.type = 'commit' AND e.timestamp > datetime('now', '-3 days')
GROUP BY r.id
ORDER BY last DESC
LIMIT 15
4. Release candidates
Repos that detected a registry package and have commits since the last release tag. Heuristic:
WITH last_tag AS (
SELECT repo_id, MAX(timestamp) AS tagged FROM events
WHERE type IN ('git_tag', 'release')
GROUP BY repo_id
),
recent_commits AS (
SELECT repo_id, COUNT(*) AS n, MAX(timestamp) AS last_commit
FROM events
WHERE type = 'commit' AND timestamp > datetime('now', '-30 days')
GROUP BY repo_id
)
SELECT r.name, p.registry, p.current_version,
rc.n AS commits_30d, lt.tagged AS last_release
FROM repos r
JOIN publications p ON p.repo_id = r.id AND p.published = 1
JOIN recent_commits rc ON rc.repo_id = r.id
LEFT JOIN last_tag lt ON lt.repo_id = r.id
WHERE (lt.tagged IS NULL OR rc.last_commit > lt.tagged)
ORDER BY rc.n DESC
LIMIT 10
5. Recently active repos with open quality gaps
WITH recent AS (
SELECT DISTINCT repo_id FROM events
WHERE type = 'commit' AND timestamp > datetime('now', '-14 days')
)
SELECT r.name, r.language,
(CASE WHEN r.has_license = 0 THEN 1 ELSE 0 END) +
(CASE WHEN r.has_readme = 0 THEN 1 ELSE 0 END) +
(CASE WHEN r.has_ci = 0 THEN 1 ELSE 0 END) AS gaps
FROM repos r
JOIN recent rc ON rc.repo_id = r.id
WHERE COALESCE(r.is_archived, 0) = 0
AND (r.has_license = 0 OR r.has_readme = 0 OR r.has_ci = 0)
ORDER BY gaps DESC
LIMIT 10
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 First seen · 129 lines · 27 tokens per session scan A 4e6504208d21
repo-sprint is a command published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 959 once invoked, about $0.0001 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-10-19.
Other commands, from other repositories
ia-document-release
Post-ship documentation sync. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, and optionally bumps the version.
ia-changelog
Create engaging changelogs for recent merges to main branch.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
release
Generate changelog, bump version, and create git tag.