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 Sistema2D/FrameCode-VibeWork --skill anti-monolith-guardgit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/anti-monolith-guard)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/anti-monolith-guard"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/anti-monolith-guard/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/sistema2d/framecode-vibework/anti-monolith-guard"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/anti-monolith-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 131 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00017 | $0.01496 |
| Opus 5 | $0.00009 | $0.00748 |
| Sonnet 5 | $0.00003 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade A, and why
anti-monolith-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 10d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Anti-Monolith Guard
Purpose
Prevent AI agents from creating or expanding monolithic files, components, routes, services, prompts, or modules. This is a Markdown-only gate: it blocks unsafe structure through explicit checklist decisions, not scripts.
Activation Triggers
Load this skill before implementation when any condition is true:
- creating a new feature, page, route, service, component, model, prompt pack, worker, or module;
- editing a file already considered large or mixed-responsibility;
- adding a second responsibility to an existing file;
- copying a similar block because "it is faster";
- retroactive instantiation finds a large application file without clear ownership;
- the plan uses vague scope such as "implement dashboard", "build backend", "create full app", or "add whole flow".
Inputs
Active plan, target artifact, responsibility map, similar-code search, dependency/consumer evidence, current size or complexity indicators, and the checks that protect behavior during a split.
Applicability Classification
Classify the target before applying numeric thresholds:
| Artifact class | Automatic size enforcement | Review focus |
|---|---|---|
| Source code, query, executable configuration, or runtime prompt | Yes, using the closest project-adjusted budget | responsibility, coupling, side effects, test boundary |
| Operational AI instruction or procedural skill | Warning by default; block only when mixed responsibilities or unsafe context loading are demonstrated | instruction hierarchy, retrieval cost, cohesion, provider neutrality |
| Canonical documentation, specification, report, plan, decision, or release record | No numeric block | cohesion, discoverability, ownership, document-graph relationships |
| Template, example, generated catalog, or historical record | No numeric block | schema correctness, generation source, reachability, preservation |
Markdown is not automatically documentary: classify it by responsibility. A Markdown prompt that controls runtime behavior may be operational, while a long technical specification may remain one cohesive document.
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.
- 10d ago First seen · 146 lines · 17 tokens per session scan A e272deb1c612
anti-monolith-guard is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (24 stars, last pushed 9d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,496 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
crap-analyzer
Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers …
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
bmad-review-edge-case-hunter
Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
ork-review-pr
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen…
ork-verify
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove, check readiness, run the relevant tests, or distinguish a claimed result from an observed one. Do not use to write missing tests or fix failures.