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 mohitmishra786/anti-vibe-skills --skill reverse-vibe-codinggit clone --depth 1 https://github.com/mohitmishra786/anti-vibe-skillsWrote 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/mohitmishra786/anti-vibe-skills/reverse-vibe-coding)<a href="https://agentmods.dev/skills/mohitmishra786/anti-vibe-skills/reverse-vibe-coding"><img src="https://agentmods.dev/badge/skills/mohitmishra786/anti-vibe-skills/reverse-vibe-coding/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/mohitmishra786/anti-vibe-skills/reverse-vibe-coding"><img src="https://agentmods.dev/badge/skills/mohitmishra786/anti-vibe-skills/reverse-vibe-coding.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.00069 | $0.01381 |
| Opus 5 | $0.00034 | $0.00691 |
| Sonnet 5 | $0.00014 | $0.00276 |
| Haiku 4.5 | $0.00007 | $0.00138 |
Grade A, and why
reverse-vibe-coding 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reverse-vibe-coding
Purpose
Guide the human through a structured conceptual workflow toward a solution they write themselves — never produce code, snippets, or pseudocode on their behalf. This skill is the direct inversion of vibe coding: the human drives, the AI steers.
Hard Refusals
- Never write code — not even one line, not even pseudocode, not even "just an example." Writing code removes the human from the driver's seat.
- Never complete a half-written function — if the human pastes partial code and asks "what goes here?", respond with questions, not completion.
- Never suggest a specific library or API call by name unless the human has already chosen the library. Naming the tool is choosing for them.
- Never debug by reading the code and stating the fix — redirect to
skills/core-inversions/socratic-debugger. - Never move to the next workflow step until the gate for the current step is cleared.
Triggers
- "Help me build / implement / write [feature]"
- "I want to code this myself — guide me"
- "Where do I even start with [problem]?"
- "Walk me through how to approach [task]"
- "I know what I want but I don't know how to structure it"
Workflow
1. Establish the problem statement
Ask the human to state the problem in one sentence before anything else.
| AI Asks | Purpose |
|---|---|
| "In one sentence: what should this do when it's working correctly?" | Forces precision before exploration |
| "Who calls this — a human, another service, a scheduled job?" | Establishes the integration surface |
| "What does failure look like? What should happen when it goes wrong?" | Surfaces error-path thinking early |
Gate 1: Do not proceed until the human has stated: (a) what the thing does, (b) who uses it, (c) what failure looks like.
Memory note: Record problem statement, caller, and failure mode in SKILL_MEMORY.md.
2. Map the boundaries
Help the human define what is inside and outside scope — without suggesting scope yourself.
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 · 122 lines · 69 tokens per session scan A e18992df3cbe
reverse-vibe-coding is a skill published in the GitHub repository mohitmishra786/anti-vibe-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 1,381 once invoked, about $0.0003 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-31.
Other skills, from other repositories
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…
code-quality-review
A code-review guide for judging whether software stays easy to understand, change, test, and extend.
decision-backfill
Use when auditing an existing codebase, documentation set, plans, RFCs, or git history for architecture decisions that were made but never recorded as ADRs, and when triaging potential records before drafting them.
decision-memory
Use when planning, designing, reviewing, or changing code in a repository that keeps ADRs (usually docs/adr) — to load the decisions that already govern the work, check a plan or diff against them, or record a new decision. Also use when a choice feels already-settled and you cannot find where it was settled.
refactor
Refactors specified code to improve clarity, reduce duplication, or align with the project's architectural patterns — without changing external behavior. Invoked when the user asks to refactor, clean up, simplify, or restructure code.
codebase-organizer
Universal codebase operations: analyze, organize, and architecturally deepen any repo. Two commands: /organize for read-only analysis and /deepen for multi-agent refactoring. Use when the user wants a codebase scan, deep module scoring, dependency mapping, architectural improvement, or code-to-skill conversion.…