direct-proving

direct-proving is a skill for Claude Code, Codex from frenzymath/Danus. It costs 44 tokens per session (1,134 once invoked), scanned A, original, Apache-2.0.

A review method that tries to prove every part of a proposed decomposition plan before accepting it. A decomposition plan breaks one difficult problem into smaller goals.

In plain words
What is it for?
Testing subgoals directly, adapting relevant existing proof ideas, and recording the exact points where a plan gets stuck.
Why use it?
It exposes missing assumptions, failed approaches, and useful counterexamples early, before the plan guides further work.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/frenzymath/danus/direct-proving
Any agent
npx skills add frenzymath/Danus --skill direct-proving
Clone the repo
git clone --depth 1 https://github.com/frenzymath/Danus

Made for: Claude Code, Codex.

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 direct-proving

README.md
[![agentmods](https://agentmods.dev/badge/skills/frenzymath/danus/direct-proving.svg)](https://agentmods.dev/skills/frenzymath/danus/direct-proving)
Your own site
<a href="https://agentmods.dev/skills/frenzymath/danus/direct-proving"><img src="https://agentmods.dev/badge/skills/frenzymath/danus/direct-proving.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,134 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00044 $0.01134
Opus 5 $0.00022 $0.00567
Sonnet 5 $0.00009 $0.00227
Haiku 4.5 $0.00004 $0.00113

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

Security

Grade A, and why

direct-proving 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 5d 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.

agents/skills/worker/direct-proving/SKILL.md · 86 lines

How it starts

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

Direct Proving

Use this skill to screen decomposition plans by first trying to carry the whole plan through, and if it does not fully go through, then identify the key stuck points.

Input Contract

Read:

  • one decomposition plan from subgoals
  • relevant immediate_conclusions, toy_examples, counterexamples, and failed_paths
  • relevant search results and references
  • any previously identified external statements whose proofs may be adaptable

Procedure

  1. Take one decomposition plan at a time.
  2. For each subgoal, actively use the searched results, toy examples, and counterexamples that are most relevant to that subgoal.
  3. When a similar theorem has been found, try to adapt its proof idea, construction, or reduction to the current subgoal instead of treating it as a black-box citation.
  4. If the adapted theorem is only a partial result with extra hypotheses, first analyze why its method needs those hypotheses and where it fails for the current subgoal — do not skip this by merely trying to show the current object satisfies the extra hypotheses and applying the partial result directly.
  5. First attempt to prove all subgoals in that plan directly.
  6. Try to carry the whole plan through before switching into failure diagnosis mode.
  7. For each subgoal, record whether it is:
    • already solved directly
    • partially advanced
    • blocked
  8. If a subgoal is blocked or you get stuck on it, FIRST invoke $construct-counterexamples for that subgoal — test whether it is false, too strong, or missing hypotheses (not merely hard). If no counterexample emerges and the subgoal still resists after at least two genuine direct attempts, do not grind indefinitely: record the stuck point as an obstacle/dead_end finding (gm_add) so siblings skip it and the next round's master_guidance can bring fresh direction.
  9. If a proof adaptation attempt fails, identify why the migration fails. Be concrete: for example, note which hypothesis is missing, which construction does not transfer, which step breaks, which counterexample blocks the migration, or which part of the searched proof depends on structure absent in the current setting.
  10. If a subgoal is solved with a self-contained partial result that the rest of the plan will USE downstream, partial-verify that result with $verify-proof in partial-candidate mode before treating it as established. Adopting unverified partial results as building blocks is the single biggest correctness risk; the verifier is the sole authority on whether the partial result really holds.
  11. If all subgoals are solved directly AND the partial results that compose into a full proof have each been partial-verified as needed, mark the plan as solved and assemble the proof draft.
  12. When a direction remains viable and supports sustained progress, work on it deeply for 1–2 hours and try to establish one mathematically deep result that resolves a genuine obstacle or materially advances the main problem. Do not turn each routine calculation into its own fact, and do not bundle shallow observations merely to imitate depth; use supporting steps to prove the one substantive conclusion.
  13. If the plan does not fully go through, then identify the key stuck points as concretely as possible.
  14. Focus on locating the decisive failure modes of the plan after this first full attempt, not on polishing a full proof.

Read the full file on GitHub · 86 lines

Files

What ships with it

1 file 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.

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. 5d ago First seen · 86 lines · 44 tokens per session scan A 9e1c22241444

Subscribe to this mod's changes

direct-proving is a skill published in the GitHub repository frenzymath/Danus (401 stars, last pushed 9d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,134 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.

Related

Other skills, from other repositories

implementation-final-review

Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…

openai/openai-agents-python · 58 tokens

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

api-docs

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.

omnigent-ai/omnigent · 50 tokens

benchmark-tune

Use this skill when running, debugging, interpreting, or documenting mesh-llm benchmark tune model-serving throughput trials, including choosing ctx/batch/ubatch/mmap/mlock/speculative-decoding sweeps, running benchmark tune on local or SSH hosts, collecting JSON evidence, and applying tolerance-aware recommendations.…

Mesh-LLM/mesh-llm · 106 tokens

deploy-windows

Use this skill when installing, deploying, launching, serving, or troubleshooting mesh-llm on a Windows machine — PowerShell install via install.ps1, flavor selection (CUDA/ROCm/Vulkan/CPU), source builds, the contrib helper scripts, and verifying it serves.

Mesh-LLM/mesh-llm · 60 tokens

research

Run deep research on any topic using the Deep Research MCP server. Use this skill whenever the user wants to research a topic, gather information, find sources, or create a research document. Triggers on: 'research this', 'find out about', 'gather information on', 'I need to understand', 'deep dive into', or any…

Arindam200/awesome-ai-apps · 78 tokens