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-challenge.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-challenge)<a href="https://agentmods.dev/commands/rizukirr/no-vibe/no-vibe-challenge"><img src="https://agentmods.dev/badge/commands/rizukirr/no-vibe/no-vibe-challenge/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-challenge"><img src="https://agentmods.dev/badge/commands/rizukirr/no-vibe/no-vibe-challenge.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.00014 | $0.00987 |
| Opus 5 | $0.00007 | $0.00494 |
| Sonnet 5 | $0.00003 | $0.00197 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
no-vibe-challenge 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/no-vibe:challenge
Generate a hands-on coding challenge. You write everything — no AI code in your files.
Arguments
$ARGUMENTS is an optional focus area. Examples:
/no-vibe:challenge— general challenge from project or session context/no-vibe:challenge error handling— challenge focused on error handling/no-vibe:challenge recursion— challenge focused on recursion
Instructions for OpenCode
1. Activate no-vibe mode
You MUST run this exact bash command:
mkdir -p .no-vibe/notes .no-vibe/refs .no-vibe/data/sessions && touch .no-vibe/active
Then verify with:
test -f .no-vibe/active
If verification succeeds, explicitly state in chat: no-vibe is active (.no-vibe/active exists).
2. Determine challenge context
Check for an active no-vibe session:
grep -rl '"status": "in_progress"' .no-vibe/data/sessions/ 2>/dev/null
If active session found:
- Read the session JSON to get topic, current layer, mode
- Generate a challenge that exercises what the user just learned
- Example: user just built a tokenizer → "Write a simple expression parser that uses your tokenizer"
If no active session:
- Analyze the user's project: Read/Grep key files to understand stack, patterns, domain
- Generate a challenge relevant to the actual codebase
- Example: project has a REST API → "Add a new endpoint with input validation from scratch"
If $ARGUMENTS provided:
- Use the focus area to narrow the challenge topic
- Combine with session/project context for relevance
3. Read the adaptation stack
Read ~/.no-vibe/PROFILE.md, .no-vibe/SUMMARY.md, and every *.md under ~/.no-vibe/user/ and .no-vibe/user/ (sorted by filename) when present. Calibrate challenge difficulty:
- PROFILE.md
## Identity & expertise/## Observed strengthsflags competence → tune scope upward. - PROFILE.md
## Known gapsflags weak areas → tune scope downward; more scaffolding. - PROFILE.md
## Disclosure moderecords the user's default disclosure preference (guidedvs.showcase) — apply the same default when sketching the challenge prompt;prediction_gate: offskips the predict-before-run micro-check. - SUMMARY.md
## Open Questionsflags concepts the user dodged in prior layers → reinforce them in the challenge. - SUMMARY.md
## Accomplishmentsshows what the user has already built → build on a recent success or revisit a recent Block area. - Any
user/*.mdfile naming an explicit constraint → respect it without re-asking.
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 · 119 lines · 14 tokens per session scan A 61b3d8250849
no-vibe-challenge is a command published in the GitHub repository rizukirr/no-vibe (36 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 987 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
adoption-sandbox
Entorno seguro de práctica — experimentar con Savia sin miedo a errores.
adoption-plan
Plan personalizado de adopción de Savia por rol — qué aprender, en qué orden.
upskill
Find the skill gaps that keep recurring across your applications and turn them into a learning plan.
re-ping
A diagnostic command that confirms the reverse-engineering add-on is installed and responds correctly. It does not read files or analyse code.
wiki-teach
Query and learn from the compiled wiki with source-grounded explanations. This is a built-in paper-wiki action.
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.