
Modonome makes steady, provable progress on technical debt a normal part of engineering. It opens small, test-backed pull requests and keeps the maker, the checker, and the merge authority as separate roles, so every change is reviewed and proven before it lands.
↗ github.com/nateshpp/modonomeAutonomy is only useful when it is trustworthy. Modonome is built to hold the tensions that matter in steady balance.
Each card shows who acts and when. Modonome plays the maker and checker; your CI runs the gates; you stay the owner and merge authority. The tag on each step names the actor.
Modonome is a prompt and a set of scripts. It runs inside a harness you already have, whether that is a coding agent, a CI job, or a human session that loads the prompt.
Each one is small enough to trust and specific enough to verify. Together they move the work that usually waits.
A clever prompt can talk another prompt into almost anything. A CI gate that runs outside the agent’s write scope answers only to your pipeline. The ratchet, the validators, and the drift guard all live there, so the guarantees hold steady even when a prompt tries to bend them.
Send one change down the pipeline and watch where it lands and which control holds the line. A held or escalated change loops back for rework, and every outcome matches a real AgentProof scenario.
{{ verdictDetail }}
AgentProof is a standalone, language-agnostic benchmark. Each of the sixteen scenarios runs a real adversarial attempt against the controls and confirms it is caught, so a passing score is verifiable evidence rather than a claim. Any agentic system can run it, which makes it a practical conformance test for the wider field, and beyond Modonome.
Trigger an event and follow it across the boundary. Some changes land in your code, some sharpen Modonome’s rules, and some upgrade Modonome itself, all inside the same repository.
Here is where Modonome is headed. A pattern proven in one repository can travel to another as verifiable evidence, and the receiving repository adopts it only after it passes that repository’s own checks. Every repository keeps its own controls, so trust is earned locally at each step rather than granted by a central authority.
v0.2 and v0.3 are planned and tracked in the repository. The milestones beyond them describe the direction we want to explore together, and the community is welcome to help shape what comes next.
Three short steps take you from a safe preview to real, verifiable evidence. Nothing changes in your repository until you choose, and autonomy waits for you to switch it on.