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 Shogo1222/socratic --skill elenchusgit clone --depth 1 https://github.com/Shogo1222/socraticWrote 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/shogo1222/socratic/elenchus)<a href="https://agentmods.dev/skills/shogo1222/socratic/elenchus"><img src="https://agentmods.dev/badge/skills/shogo1222/socratic/elenchus/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/shogo1222/socratic/elenchus"><img src="https://agentmods.dev/badge/skills/shogo1222/socratic/elenchus.svg" alt="Reviewed on agentmods" width="80" 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.00119 | $0.05366 |
| Opus 5 | $0.00060 | $0.02683 |
| Sonnet 5 | $0.00024 | $0.01073 |
| Haiku 4.5 | $0.00012 | $0.00537 |
Grade A, and why
elenchus 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elenchus
Challenge a test suite with plausible misunderstandings of programming intent. Optimize for confidence in important behavior, not mutation score. Mutation is the internal evidence engine, not the headline: report each result as the incident it represents, never as an operator name or a score.
Required references
Read references/mutation-design.md before generating mutants and references/safety.md before changing or executing code. When a proposed test is proved or applied, read references/test-handoff.md. In standalone use only, validate inputs and outputs with the bundled intent-contract.schema.json, mutation-result.schema.json, mutation-report.schema.json, and test-handoff.schema.json. Under a Socratic-hosted run, never open schema files: every document starts from a Runner scaffold whose editable_fields and field_guide carry the authoritative structure, and the Runner performs all validation.
Git safety boundary
Use local Git only for strictly read-only evidence gathering. Allowed commands are limited to git diff, git show, git log, git rev-parse, git merge-base, and git ls-files; git archive is not read-only (-o writes a file) and the Host gate denies it. During an active hook-host run, prefix each with git --no-pager; add --no-ext-diff --no-textconv to diff, show, and log. Never change local or remote Git state. Never run any staging, commit, amend, push, pull, fetch, checkout, switch, reset, stash, merge, rebase, cherry-pick, branch, tag, or worktree operation. Never invoke gh or a code-host write API. Do not request permission to perform a prohibited operation.
Materialize Base and Head as disposable filesystem snapshots without branch switching or Git worktrees. If the required object is unavailable locally and obtaining it would require fetch, stop and report the snapshot as unavailable.
What ships with it
9 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.
- agents/openai.yaml 223 B
- references/intent-contract.schema.json 7.6 KB
- references/mutation-design.md 3.3 KB
- references/mutation-report.schema.json 16 KB
- references/mutation-result.schema.json 4.9 KB
- references/safety.md 5.0 KB
- references/test-handoff.md 2.7 KB
- references/test-handoff.schema.json 3.7 KB
- scripts/isolation_gate.py 6.4 KB runs code
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.
- 9d ago First seen · 279 lines · 119 tokens per session scan A 7e35a8f337ba
elenchus is a skill published in the GitHub repository Shogo1222/socratic (5 stars, last pushed 1mo ago), licensed MIT. It adds 119 tokens to every session and 5,366 once invoked, about $0.0006 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
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.