ndv-adversarial

ndv-adversarial is a skill for Claude Code from emb715/neurodiveragents. It costs 50 tokens per session (347 once invoked), scanned A, original, MIT.

A testing discipline that looks for failures instead of checking only the normal case.

In plain words
What is it for?
Use it to design and review tests for boundary conditions, bad inputs, dependency failures, and teardown or repeated-call states.
Why use it?
It exposes bugs involving empty, invalid, extreme, repeated, concurrent, or failing inputs and dependencies.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to design and review tests for boundary conditions, bad inputs, dependency failures, and teardown or repeated-call states.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/emb715/neurodiveragents/ndv-adversarial
Install

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.

Any agent
npx skills add emb715/neurodiveragents --skill ndv-adversarial
Clone the repo
git clone --depth 1 https://github.com/emb715/neurodiveragents

Made for: Claude Code.

Wrote 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.

agentmods badge for ndv-adversarial

README.md
[![agentmods](https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-adversarial/github.svg)](https://agentmods.dev/skills/emb715/neurodiveragents/ndv-adversarial)
Your own site
<a href="https://agentmods.dev/skills/emb715/neurodiveragents/ndv-adversarial"><img src="https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-adversarial/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.

agentmods 80×15 button for ndv-adversarial

Your own site · 80×15
<a href="https://agentmods.dev/skills/emb715/neurodiveragents/ndv-adversarial"><img src="https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-adversarial.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00347
Opus 5 $0.00025 $0.00173
Sonnet 5 $0.00010 $0.00069
Haiku 4.5 $0.00005 $0.00035

Measured 9d ago against content hash d7b7f9e3f831, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ndv-adversarial 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 9d 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.

skills/ndv-adversarial/SKILL.md · 38 lines

What it actually says

You assume the code is lying. The happy path is a story the developer told themselves to ship on Friday. Every function is guilty of hiding a bug until you personally prove otherwise. You are not pessimistic — you are adversarial. Pessimists give up; you write another test case.

Primordial rule: The happy path is not proof. It is an alibi. Code that passes the happy path has proven exactly one thing: it works when nothing goes wrong. That is the least useful thing you can know.

Constraints:

  • Test adversarial cases first, happy path last
  • For every input: what if null? wrong type? empty? oversized? malicious?
  • For every dependency: what if it fails? times out? returns empty?
  • For every state: what if called twice? called after teardown? concurrent access?
  • Boundary conditions: 0, 1, -1, max, max+1, empty, single element
  • A test with no assertions is decoration, not verification

Never:

  • Accept happy path tests as sufficient
  • Trust code that hasn't been tested adversarially
  • Skip boundary conditions
  • Celebrate coverage percentage over coverage quality
  • Write tests that cannot fail
Changes

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.

  1. 9d ago First seen · 38 lines · 50 tokens per session scan A d7b7f9e3f831

Subscribe to this mod's changes

ndv-adversarial is a skill published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 347 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.

Related

Other skills, from other repositories

hotfix

Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…

pe-menezes/vibeflow · 102 tokens

vibeflow-hotfix

Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Use when a defect was observed and the evidence is in hand — an error message, a failing log, real data misbehaving — wherever…

pe-menezes/vibeflow · 103 tokens

vibeflow-audit

Audits implementation against its DoD and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. With --consolidate-hotfixes, reclassifies hotfix trace docs against the…

pe-menezes/vibeflow · 86 tokens

screen-reader-testing

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

wshobson/agents · 39 tokens

temporal-python-testing

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

wshobson/agents · 45 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens