formal-correctness

formal-correctness is a skill for Claude Code from cdeust/zetetic-team-subagents. It costs 68 tokens per session (668 once invoked), scanned A, original, MIT.

A reasoning method for proving that correctness-critical software follows a written specification. It focuses on rules that must always hold, not only on tests that happened to pass.

In plain words
What is it for?
Designing and reviewing concurrent or distributed code, specifying interfaces, checking whether implementations can be substituted safely, and analysing whether a problem is decidable.
Why use it?
Tests cannot cover every failure in concurrent or distributed systems, where timing and partial failures can create rare bugs.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the zetetic-team-subagents plugin — 16 skills, 2 commands, 23 agents, 7 hooks, 1 MCP server shipped together

Good fit Designing and reviewing concurrent or distributed code, specifying interfaces, checking whether implementations can be substituted safely, and analysing whether a problem is decidable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cdeust/zetetic-team-subagents/formal-correctness
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 cdeust/zetetic-team-subagents --skill formal-correctness
Clone the repo
git clone --depth 1 https://github.com/cdeust/zetetic-team-subagents

Made for: Claude Code.

Or install zetetic-team-subagents, the plugin that ships this one along with the rest of its 16 skills, 2 commands, 23 agents, 7 hooks, 1 MCP server.

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 formal-correctness

README.md
[![agentmods](https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/formal-correctness/github.svg)](https://agentmods.dev/skills/cdeust/zetetic-team-subagents/formal-correctness)
Your own site
<a href="https://agentmods.dev/skills/cdeust/zetetic-team-subagents/formal-correctness"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/formal-correctness/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 formal-correctness

Your own site · 80×15
<a href="https://agentmods.dev/skills/cdeust/zetetic-team-subagents/formal-correctness"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/formal-correctness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 668 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.00068 $0.00668
Opus 5 $0.00034 $0.00334
Sonnet 5 $0.00014 $0.00134
Haiku 4.5 $0.00007 $0.00067

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

Security

Grade A, and why

formal-correctness 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 11d 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/formal-correctness/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Formal Correctness

Problem shape: correctness-critical code (concurrency, distribution, protocol, contract) whose failure modes tests cannot exercise. The move: specification before code, invariants before traces, contracts before implementations, decidability before optimization.

Relevant geniuses

Agent Use when
lamport distributed design uses wall-clock ordering; no written spec; correctness argued by example executions; partial failure ignored
dijkstra code and correctness argument must be developed together; a construct defeats local reasoning; tests can't cover the failure mode
liskov swapping an implementation breaks callers; interfaces with types but no behavioral contract; composition breaks what components pass alone
turing problem drowning in detail — reduce to the simplest machine; check decidability/complexity class before investing; vague concept needs an operational test
godel the system reasons about itself (self-hosting, self-validating, self-referential rules) — find the incompleteness before it finds you
alkhwarizmi messy problem needs a canonical form and an exhaustive case classification before an algorithm exists
panini a sprawling rule set needs a compact generative specification with explicit conflict-resolution ordering

Invocation

  1. Pick the best-fit agent above. If two or more fit, run tools/genius-invoker.sh route "<problem>" and take the top ranked match.
  2. Load it: tools/genius-invoker.sh invoke <agent> "<problem>", then read agents/genius/<agent>.md in full.
  3. Apply the agent's <workflow> step by step and answer in its <output-format>. The deliverable is a spec, invariant, or contract the code refines — not a narrative that it "looks right".
  4. Typical chain: turing bounds what is decidable → lamport writes the spec → dijkstra derives the code → liskov contracts the interfaces. Run pairs via tools/genius-invoker.sh compose lamport dijkstra -- "<problem>".
  5. If no shape above matches, use a standard team agent instead.

Read the full file on GitHub · 50 lines

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. 11d ago First seen · 50 lines · 68 tokens per session scan A dab70955b737

Subscribe to this mod's changes

formal-correctness is a skill published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 668 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