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 queelius/claude-anvil --skill workflowsgit 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/skills/queelius/claude-anvil/workflows)<a href="https://agentmods.dev/skills/queelius/claude-anvil/workflows"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/workflows/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/queelius/claude-anvil/workflows"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/workflows.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.00062 | $0.01305 |
| Opus 5.5 | $0.00025 | $0.00522 |
| Sonnet 5.5 | $0.00012 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
workflows 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repoindex: which tool for which task
The plugin exposes three layers. Pick the smallest one that answers the question.
| Layer | Use when |
|---|---|
MCP tool calls (run_sql, get_manifest) |
Single question, clear query, one answer. |
Slash commands (/repo-week, /repo-status, /repo-audit, /repo-sprint, /repo-mirror) |
Named recurring task with a fixed shape. |
Agents (repo-doctor, repo-polish, repo-explorer) |
Multi-step reasoning, prose synthesis, or file writing. |
Picking the layer
Use raw MCP when the user asks one question
"Show me my Python repos" is one run_sql. Do not invoke an agent. Do not reach for a slash command.
SELECT name, path FROM repos WHERE language = 'Python' ORDER BY name
Same for "how many repos do I have", "which repos are on PyPI", "what are my most starred repos". Direct SQL wins.
Use a slash command for recurring shaped queries
These have a known output format and the user invokes them by name:
/repo-week [Nd]: weekly activity. Top churn, releases, dormant-wake, totals./repo-status [name]: collection overview or single-repo detail card./repo-audit [filters]: read-only summary ofops auditfindings./repo-sprint: "what's open?" kickoff context (dirty, unpushed, recent, release candidates)./repo-mirror [flags]: dry-run-first wrapper aroundops mirrorfor redundancy pushes.
Slash commands never write files on their own (mirror is the one exception, and only with --force-real).
Use an agent for multi-step or prose work
repo-doctor: fixed triage workflow. "What needs attention?" Produces a prioritized action list.repo-polish: single-repo release prep. Audits, generates citation/license/codemeta, writes README improvements, syncs GitHub metadata. Writes files.repo-explorer: open-ended analysis. Custom SQL across multiple tables with narrative synthesis.
Common patterns
Language-filtered audit
/repo-audit --language python --severity critical
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 · 123 lines · 62 tokens per session scan A a30be3bfd065
workflows is a skill published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,305 once invoked, about $0.0002 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 skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
product
Apply product thinking to platform work — DevEx audits, friction analysis, RFC/ADR drafting, incident communication, post-mortems, capacity planning, cost optimisation, and platform health review.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).