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 mracal/vibe-engineering --skill scope-guardgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/scope-guard)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/scope-guard"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/scope-guard.svg" alt="Measured on agentmods" 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.00031 | $0.00603 |
| Opus 5 | $0.00015 | $0.00302 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
vibe-scope-guard 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 6d 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.
This is a copy
100% identical to vibe-scope-guard — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-scope-guard
The best code is the code you don't write. Stay focused on what was asked.
When to Use This Skill
- During any implementation task
- When you notice you're "improving" code that wasn't in the request
- When implementation is taking longer than expected
- When you're about to create an abstraction "for later"
When NOT to Use This Skill
- During brainstorming (ideas should be unconstrained)
- When the user explicitly asks for broad improvements
- When scope expansion is necessary for correctness
Scope Creep Signals
Watch for these patterns:
| Signal | Example | Response |
|---|---|---|
| Unrequested features | "While I'm here, let me add caching" | Stop. Was caching requested? |
| Premature abstraction | "Let me create a generic helper for this" | Is it used more than once? |
| Gold plating | "Let me add comprehensive error messages for every case" | Only at system boundaries |
| Refactoring drive-by | "This function could be cleaner" | Was refactoring requested? |
| Over-engineering | "Let me make this configurable" | Does anyone need configuration? |
| Documentation creep | "Let me add docstrings to all these functions" | Only to functions you changed |
| Test over-expansion | "Let me test every possible input" | Test the boundaries, not every input |
The Rule
Three similar lines of code is better than a premature abstraction.
Before adding anything not explicitly requested, ask:
- Was this requested? → No → Don't do it
- Is it necessary for correctness? → No → Don't do it
- Will it break without this? → No → Don't do it
- Is the user watching time/cost? → Yes → Definitely don't do it
Steps
When you detect scope creep:
- Stop — Don't commit the extra work
- Acknowledge — "I notice I'm adding [X] which wasn't requested"
- Offer — "Would you like me to also [X], or should I stay focused on [original task]?"
- If declined — Revert the extra work, continue with original scope
- If accepted — Proceed, but track it separately
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.
- 6d ago First seen · 69 lines · 31 tokens per session scan A 7682bea04b6d
vibe-scope-guard is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 603 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-scope-guard, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
unity-ui-art-and-motion-production
Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…
game-screenshot-showcase-and-store-packaging
Use when a Unity team needs approved PlayMode screenshots, immutable capture evidence, reviewed showcase slides, or report-only store screenshot packaging without auto-upload, signing, or submission.
studio-project-scaffold
Use when running gamestudio init, status, or uninit, or bootstrapping a new or adopted game repository with AGENTS.md, HANDOFF.md, .agents/CONTRACT.md, project governance, a subsystem registry, or a per-project adapter report, plan digest, named reviewer, backup root, generated agent overlay, apply, uninstall, and…
using-game-studio-skills
Use when starting any GameStudio-CodexKIT task or when a model runner is unavailable and someone requests a confidence-based PASS.
animation-rigging-import-audit
Use when character animation needs an audit across skeleton, rig, skin weights, avatar, retargeting, clips, events, root motion, compression, import settings, runtime blending, and platform budgets; not for general art preflight.