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 antithesishq/antithesis-skills --skill antithesis-researchgit clone --depth 1 https://github.com/antithesishq/antithesis-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/antithesishq/antithesis-skills/antithesis-research)<a href="https://agentmods.dev/skills/antithesishq/antithesis-skills/antithesis-research"><img src="https://agentmods.dev/badge/skills/antithesishq/antithesis-skills/antithesis-research/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/antithesishq/antithesis-skills/antithesis-research"><img src="https://agentmods.dev/badge/skills/antithesishq/antithesis-skills/antithesis-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 34 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00049 | $0.03350 |
| Opus 5 | $0.00024 | $0.01675 |
| Sonnet 5 | $0.00010 | $0.00670 |
| Haiku 4.5 | $0.00005 | $0.00335 |
Grade A, and why
antithesis-research 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antithesis Research
Skill version: 2026-09-08 2e4a837
Purpose and Goal
Research a target system and produce scratchbook artifacts that unblock the rest of the workflow. Success means:
antithesis/scratchbook/sut-analysis.mdcaptures architecture, state, concurrency, and failure-prone areasantithesis/scratchbook/property-catalog.mdlists concrete, testable properties with prioritiesantithesis/scratchbook/deployment-topology.mddescribes the minimal useful container topologyantithesis/scratchbook/properties/{slug}.mdcaptures per-property evidence trails and contextantithesis/scratchbook/property-relationships.mdmaps suspected clusters and connections between propertiesantithesis/scratchbook/evaluation/synthesis.mdrecords categorized evaluation findings and actions taken
Prerequisites and Scoping
At the start of every research run, ask the user about external references:
Before I start, are there docs, design notes, related repos, issue trackers, or anything else outside this directory tree that I should also consult? "Just this directory" is fine.
Capture the answer verbatim. Each external reference becomes a path (or URL) plus a brief why note. The orchestrator (this skill) holds the answer for the full duration of the run and threads it as input to every reference workflow that produces a top-level artifact: sut-discovery.md, sut-analysis.md, property-discovery.md, deployment-topology.md, property-evaluation.md. Each of those references' agent-instruction sections accepts the list as input. The list is also recorded in the provenance frontmatter of every top-level artifact (see references/scratchbook-setup.md). Any agent that receives the external references treats each as a lead to validate, not a fact — see references/validating-claims.md.
Beyond the scope question, ask only for blockers or scoping decisions you cannot infer safely:
- The repo or codebase location, if it is not already clear
- Which subsystem or component matters most, if the work is narrower than the whole repo
- Known incidents, closed bugs, or specific failure modes worth targeting
What ships with it
10 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.
- references/deployment-topology.md 4.9 KB
- references/faults.md 7.8 KB
- references/property-catalog.md 16 KB
- references/property-discovery.md 19 KB
- references/property-evaluation.md 16 KB
- references/scratchbook-artifacts.md 5.4 KB
- references/scratchbook-setup.md 4.9 KB
- references/sut-analysis.md 4.9 KB
- references/sut-discovery.md 11 KB
- references/validating-claims.md 4.6 KB
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 Changed 976a35a3741b
- 8d ago Changed 4397970ac422
- 12d ago First seen · 188 lines · 49 tokens per session scan A 1d8e1bc190c3
antithesis-research is a skill published in the GitHub repository antithesishq/antithesis-skills (267 stars, last pushed 3d ago), licensed Apache-2.0. It adds 49 tokens to every session and 3,350 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-30.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
train-pose
Train/evaluate WiFi pose models honestly — camera-supervised (MediaPipe + CSI) and camera-free (WiFlow), always checked against the mean-pose baseline before any PCK is quoted.
experiment-audit
A review step that checks whether an experiment's reported results are supported by real data and a sufficiently broad test.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.
i4h-catheter-navigation-smoke
Run CPU-only fluorosim smoke tests (imports, preprocessing, CLI parsers). Use when asked to smoke-test catheter navigation in CI or without a GPU.