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/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/commit)<a href="https://agentmods.dev/commands/muyen/vibe-to-prod/commit"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/commit/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/muyen/vibe-to-prod/commit"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/commit.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.00009 | $0.00224 |
| Opus 5.5 | $0.00004 | $0.00090 |
| Sonnet 5.5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
commit 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 12d 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
Create Commit
Create a well-formatted commit following conventional commit conventions.
Process
- Check git status to see changes
- Review the diff to understand what changed
- Stage appropriate files
- Create commit with conventional format
Commit Format
type: description
Types:
- feat: New feature
- fix: Bug fix
- docs: Documentation
- style: Formatting (no code change)
- refactor: Code restructuring
- test: Adding tests
- chore: Maintenance
Pre-Commit Checklist
- Tests pass
- No secrets in code
- Commit message is clear
- Only relevant files staged
Commands
# Check status
git status
# View changes
git diff
# Stage files
git add -A # or specific files
# Commit
git commit -m "type: description"
# Push
git push
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.
- 12d ago First seen · 57 lines · 9 tokens per session scan A b269cd3ae966
commit is a command published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 224 once invoked, about $0.0000 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-04.
Other commands, from other repositories
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
constitution
Add, update, or remove engineering principles in docs/project/engineering-principles.md with atomic versioned commits.
commit
Commit current changes following project commit rules (template, body settings).
run-task
Run pending steps, then aftertask finalization; does not close the task.
finish-task
Deprecated alias for close-task.
gh-review-fix-loop
Fix and resolve GitHub PR review threads.