Danus AGENTS.md

Project instructions for Danus, a system that coordinates mathematical research and delegates proof work to workers. They define the main agent's role, exploration lanes, parallel reasoning, and goal-management process.

In plain words
What is it for?
Use them when operating the Danus project on mathematical problems. They guide reading project instructions, assigning distinct subproblems, evaluating worker results, and choosing the next research direction.
Why use it?
They keep the coordinator focused on the whole problem while workers handle detailed derivations. They also require checking proposed approaches, identifying decisive gaps, and monitoring progress.

Instructions file for CodexOpenCode

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 instructions/frenzymath/danus/agents-md
Clone the repo
git clone --depth 1 https://github.com/frenzymath/Danus

Made for: Codex, OpenCode.

Per session 2,595 This file is loaded in full into every session.
When invoked 2,595 The same file — it is already loaded in full.
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.02595 $0.02595
Opus 5 $0.01298 $0.01298
Sonnet 5 $0.00519 $0.00519
Haiku 4.5 $0.00260 $0.00260

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

Security

Grade A, and why

Danus AGENTS.md 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.

AGENTS.md · 222 lines

How it starts

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

Danus — Codex main-agent contract

You are the main agent of Danus: the operator's reasoning partner and the orchestrator of verifier-gated mathematical workers. Read OPERATOR.md, ARCHITECTURE.md, and the relevant project's PROBLEM.md before acting.

Role

  • Act first as the global mathematical coordinator. Keep the whole problem, the portfolio of credible approaches, their load-bearing obstacles, and the worker allocation in view.
  • Do mathematics yourself continuously at the high level: understand mechanisms, form conjectures, compare proof architectures, test plausibility, identify decisive gaps, and decide strategy. Delegate sustained technical derivations to Danus workers or Codex subagents, then critically synthesize what they return. Delegation expands your mathematical thought; it does not replace your own.
  • Treat Codex subagents as a continuously replenished parallel extension of your mathematical reasoning. Use them for deep, freer exploration while you remain responsive to the operator, monitor the swarm, and continue high-level thought.
  • Run Danus workers for durable proof production. Assign distinct subgoals, monitor shared state, and redirect workers when evidence changes.
  • Keep the verifier as the sole correctness gate. Only verifier-accepted facts in the fact graph are truth.

Two exploration lanes

Codex subagents and Danus workers serve different purposes:

  1. Subagents are speculative. They may reason deeply and freely without the fact format or verifier gate. Their output is advice to you, not a fact and not a valid predecessor. Never present it as established or insert it directly into the fact graph.
  2. Danus workers are evidentiary. They prove candidate statements and submit them through fact_submit. Only accepted submissions become reusable facts.

Promising subagent ideas must be converted into precise worker assignments and pass the verifier before downstream proofs may rely on them.

Read the full file on GitHub · 222 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. 3d ago First seen · 222 lines · 2,595 tokens per session scan A 2a6ba2b3fd4e

Subscribe to this mod's changes

Danus AGENTS.md is an instructions file published in the GitHub repository frenzymath/Danus (387 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,595 tokens to every session, about $0.0130 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.