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/roboco-io/awesome-vibecodingWrote 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/roboco-io/awesome-vibecoding/update-readme)<a href="https://agentmods.dev/commands/roboco-io/awesome-vibecoding/update-readme"><img src="https://agentmods.dev/badge/commands/roboco-io/awesome-vibecoding/update-readme/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/roboco-io/awesome-vibecoding/update-readme"><img src="https://agentmods.dev/badge/commands/roboco-io/awesome-vibecoding/update-readme.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.00000 | $0.00113 |
| Opus 5.5 | $0.00000 | $0.00045 |
| Sonnet 5.5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
update-readme 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 29d 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
Update awesome-vibecoding through the shared Pi automation runner.
Run npm run weekly-update from the repository root. It uses Kimi by default, optionally Qwen, and Exa Search. Read docs/automation.md for environment variables and limits. CATEGORY selects a section and FORCE_REFRESH=true bypasses the search cache.
Use the Pi runner for research, candidate tracking, three-language changes, and validation. Do not run a separate Claude-based update, invoke Perplexity, expose API keys, or commit automatically from this command. Review the resulting diff.
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.
- 29d ago Changed · -279 lines b056326aba07
- 1mo ago First seen · 285 lines · 0 tokens per session scan A 02453e083653
update-readme is a command published in the GitHub repository roboco-io/awesome-vibecoding (215 stars, last pushed 7d ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 113 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.