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.
npx skills add rizukirr/no-vibe --skill no-vibe-btwgit 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/skills/rizukirr/no-vibe/no-vibe-btw)<a href="https://agentmods.dev/skills/rizukirr/no-vibe/no-vibe-btw"><img src="https://agentmods.dev/badge/skills/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/skills/rizukirr/no-vibe/no-vibe-btw"><img src="https://agentmods.dev/badge/skills/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.00029 | $0.00546 |
| Opus 5 | $0.00015 | $0.00273 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
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 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
no-vibe-btw
Temporarily disable no-vibe for one scoped task, perform the task, then restore no-vibe if it was previously active.
Inputs
Text after $no-vibe-btw is the required task description.
Examples:
$no-vibe-btw add a .gitignore for node$no-vibe-btw scaffold a Makefile with build/test/clean targets$no-vibe-btw fix typo in README.md line 42
Workflow
1. Validate task
If task text is missing, 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
Run:
was_active=0
[ -f .no-vibe/active ] && was_active=1
3. Disable guard for this task
Run:
rm -f .no-vibe/active
Verify:
test ! -f .no-vibe/active
If verified, state: temporary btw mode active (.no-vibe/active removed).
4. Execute exactly one task
Do exactly what the task asks, nothing more.
Scope rules:
- One task only; no extra cleanup or opportunistic refactors.
- No abstractions beyond task requirements.
- If task is ambiguous or too broad, ask user to narrow scope before editing.
5. Restore marker
Always restore marker if it was active before, even on failure:
if [ "$was_active" = "1" ]; then
mkdir -p .no-vibe && touch .no-vibe/active
fi
Verify:
if [ "$was_active" = "1" ]; then
test -f .no-vibe/active
fi
If verified and was_active=1, state: no-vibe is active again (.no-vibe/active restored).
6. Report
Give one short summary of files changed and why.
Hard rules
- Single-task, one-shot behavior only.
- Always restore
.no-vibe/activewhen it was previously active. - Do not modify
.no-vibe/contents unless task explicitly targets them. - If user wants no-vibe disabled entirely, route to
$no-vibe off.
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 · 90 lines · 29 tokens per session scan A 9354a80958d1
no-vibe-btw is a skill published in the GitHub repository rizukirr/no-vibe (36 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 546 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 skills, from other repositories
taiyi-plan
A TaiyiForge planning step that turns a README, product requirements document, or technical plan into a list of separate project changes. Each change includes a suggested work profile, dependencies, and priority.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.