Borrowing it
Nothing to install: this file belongs to rizukirr/no-vibe. 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/rizukirr/no-vibe/main/.opencode/commands/no-vibe-btw.mdgit clone --depth 1 https://github.com/rizukirr/no-vibeWrote 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/rizukirr/no-vibe/no-vibe-btw)<a href="https://agentmods.dev/commands/rizukirr/no-vibe/no-vibe-btw"><img src="https://agentmods.dev/badge/commands/rizukirr/no-vibe/no-vibe-btw/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/rizukirr/no-vibe/no-vibe-btw"><img src="https://agentmods.dev/badge/commands/rizukirr/no-vibe/no-vibe-btw.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.00023 | $0.00650 |
| Opus 5 | $0.00012 | $0.00325 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
no-vibe-btw 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/no-vibe-btw
One-shot escape from no-vibe mode. AI writes code to project files for a single task, then restores the no-vibe marker if it was active.
Use when you hit something tedious or boilerplate you would rather not type yourself, but want learning mode back on for the rest of the session.
Arguments
$ARGUMENTS — the task description. Required.
Examples:
/no-vibe-btw add a .gitignore for node/no-vibe-btw scaffold a Makefile with build/test/clean targets/no-vibe-btw fix the typo in README.md line 42
Instructions for OpenCode
1. Validate arguments
If $ARGUMENTS is empty, stop and tell the user:
/no-vibe-btw requires a task description. Example: /no-vibe-btw add a .gitignore for node.
2. Snapshot marker state
You MUST run:
was_active=0
[ -f .no-vibe/active ] && was_active=1
3. Disable no-vibe guard for this one task
You MUST run:
rm -f .no-vibe/active
Then verify with:
test ! -f .no-vibe/active
If verification succeeds, explicitly state in chat: temporary btw mode active (.no-vibe/active removed).
4. Execute the task
Do exactly what $ARGUMENTS asks — nothing more.
Scope rules:
- One task only. No scope creep, no "while I am here" cleanup.
- No refactors of untouched code.
- No new abstractions beyond what the task requires.
- If the task is ambiguous or too broad (for example "build the whole app"), stop and ask the user to narrow it before writing anything.
5. Restore marker state
Always restore if it was active before, even if the task failed:
if [ "$was_active" = "1" ]; then
mkdir -p .no-vibe && touch .no-vibe/active
fi
Then verify with:
if [ "$was_active" = "1" ]; then
test -f .no-vibe/active
fi
If verification succeeds and was_active=1, explicitly state in chat: no-vibe is active again (.no-vibe/active restored).
6. Report
One short summary: what changed (files + one-line rationale). No trailing narration.
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.
- 11d ago First seen · 93 lines · 23 tokens per session scan A 6453bfb9b746
no-vibe-btw is a command published in the GitHub repository rizukirr/no-vibe (36 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 650 once invoked, about $0.0001 per session on Opus 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
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
pn-delight
Add purposeful moments of joy, motion, and personality. Use when the design is correct and complete but feels flat and lifeless.
pn-frontend-redo
Audit-driven frontend remediation on an existing app — baseline audit, slice plan, sequential UI slices with maker-checker gates, preflight, deliver. Use instead of pn-program for same-repo sequential surfaces (Home → fight → chrome). Not for greenfield (pn-design) or parallel vertical slices (pn-program).
pn-audit-api
Surgical API design review — REST conventions, status codes, response shapes, validation, and schema leaks. Use standalone or as part of pn-backend-audit. Outputs a scored fix roadmap.
pn-audit-errors
Standardize error handling — consistent shapes, structured logging, correlation IDs, safe client responses. Surgical command for error handling. Use standalone or as part of pn-backend-audit.
pn-audit-security
OWASP-guided security review — auth posture, input validation, secrets, CORS, JWT, rate limiting. Surgical command for backend security. Use standalone or as part of pn-backend-audit.