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 agentmods add skills/localplugins/plugins/anti-fake-greennpx skills add localplugins/plugins --skill anti-fake-greengit clone --depth 1 https://github.com/localplugins/pluginsWrote 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/localplugins/plugins/anti-fake-green)<a href="https://agentmods.dev/skills/localplugins/plugins/anti-fake-green"><img src="https://agentmods.dev/badge/skills/localplugins/plugins/anti-fake-green.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 | $0.00044 | $0.00573 |
| Opus 5 | $0.00022 | $0.00287 |
| Sonnet 5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
anti-fake-green 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 3d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-Fake-Green
Green must mean the code is actually correct. Making red go green by cheating is worse than leaving it red, because it hides the bug. These rules are non-negotiable.
Use when
- Fixing a failing test or a type/compile error (as
fixer). - Writing or updating a test (as
test-writer). - Judging whether a change is a real fix or a cheat (as
green-guardian).
The one rule
Change the smallest amount of production code (or a genuinely-wrong test) needed to make the check pass for the right reason — never suppress the signal.
Fake-green, at a glance
Reject any change that does one of these instead of fixing the cause:
- Removes the test — skip / delete / comment out /
.skip/.only/xit/xdescribe/@pytest.mark.skip. - Weakens the assertion — loosen an expected value,
toEqual→toBeTruthy, delete assertions. - Silences the error —
@ts-ignore,eslint-disable,# type: ignore, emptycatch {},except: pass. - Widens the type — to
any/unknown/objectjust to clear a type error. - Pads coverage — tests that assert nothing or only that a mock was called.
- Bends the test to the bug — editing the test to match buggy behavior when the code is wrong.
Decision guide
- Is production code wrong, or is the test wrong? Fix whichever is genuinely at fault; default to production code.
- Would this change survive
green-guardian's diff inspection? If it matches any fake-green pattern above, it fails — redo it. - Can you prove it with revert-verification? If not, you haven't proven green.
- Can't make it genuinely green? Stop and report exactly what's blocking. Never fake it.
Deep references
references/fake-green-patterns.md— side-by-side fake-green vs. real-fix examples in JS/TS, Python, Go, and Rust, plus the full rejection cataloggreen-guardianapplies.references/revert-verification.md— the step-by-step procedure to prove a fix or a new test is real, usinggit stash/ file checkout, with commands and pitfalls.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 42 lines · 44 tokens per session scan A de91d53bcc2c
anti-fake-green is a skill published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 573 once invoked, about $0.0002 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
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
growth-loops
Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms, building product-led traction, or understanding how growth loops work.