Borrowing it
Nothing to install: this file belongs to Minh-Tam-Solution/EndiorBot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Minh-Tam-Solution/EndiorBot/main/.claude/commands/vibecoding.mdgit clone --depth 1 https://github.com/Minh-Tam-Solution/EndiorBotWrote 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/minh-tam-solution/endiorbot/vibecoding)<a href="https://agentmods.dev/commands/minh-tam-solution/endiorbot/vibecoding"><img src="https://agentmods.dev/badge/commands/minh-tam-solution/endiorbot/vibecoding/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/minh-tam-solution/endiorbot/vibecoding"><img src="https://agentmods.dev/badge/commands/minh-tam-solution/endiorbot/vibecoding.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.00008 | $0.00207 |
| Opus 5.5 | $0.00003 | $0.00083 |
| Sonnet 5.5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
vibecoding 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 1mo 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
Calculate Vibecoding Index
THIN CLIENT: Calls EndiorBot core. NO business logic here.
! ./endiorbot.mjs vibecoding $ARGUMENTS
Output includes:
- Overall score (0-100, lower is better)
- Zone (green/yellow/orange/red)
- 6 metrics breakdown:
- Complexity (cyclomatic)
- Test Coverage
- Lint Errors
- Security Issues
- Doc Coverage
- TODO Count
Thresholds
- <= 30: Green (excellent) - Ship with confidence
- 31-60: Yellow (acceptable) - Review recommended
- 61-80: Orange (warning) - Significant review required
- 81-100: Red (critical) - Block until fixed
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.
- 1mo ago First seen · 32 lines · 8 tokens per session scan A 543037004850
vibecoding is a command published in the GitHub repository Minh-Tam-Solution/EndiorBot (19 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 207 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-08-30.
Other commands, from other repositories
vs-queue
Show what is waiting on the operator, then the live / in-flight board tasks.
vs-stop
Gracefully close the Vibe Squad tmux session from inside Chrono.
brain-stats
Show claudectl brain learning metrics — accuracy, correction rate, and effectiveness.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).
next
Suggest the most likely next workflow action based on current context.