optimus

Boots a harness-first dev-mode repair loop by loading invariant policies and playbooks before any code edit.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/Tcuzzo/HydraAgent_public --skill optimus-tcuzzo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: optimus
Source: https://github.com/Tcuzzo/HydraAgent_public/tree/main/skills/optimus
Command: npx skills add https://github.com/Tcuzzo/HydraAgent_public --skill optimus-tcuzzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents drift when they work from model memory instead of grounded rules, producing fabricated APIs, unverified claims, and regressions. This Skill forces every session to load the invariant map and a structured repair loop before any design or edit happens. ## Core Features & Use Cases - Harness-first boot sequence: Loads the invariant map (.hydraAgent/policies/backs-invariants.yaml), the dev-mode playbook, and companion skills (the_path, elite_build_understanding) before any work begins. - Seven-step repair loop: Reproduce on live truth, write a failing RED contract test, fix the flaw class at the seam, verify on the real path, get an independent grade from a different model family, check concurrent sessions, then land. - Anti-hallucination discipline: Requires resolving every symbol against the installed artifact, falsifying your own change, and never claiming green off a mock or proxy. - Use Case: Before fixing a bug in a shared repo, invoke this Skill so the agent reproduces the failure live, writes a regression test that fails for the real reason, fixes the entire flaw class, and reports PROVEN or STILL-BUILDING. ## Quick Start Invoke the optimus skill to boot the harness-first dev-mode loop before starting any coding task in this repository.

Frequently Asked Questions about optimus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent an AI coding agent from hallucinating APIs?▼

Ground the agent in a harness that supplies invariants and repo truth instead of model priors. This Skill requires resolving every symbol against the installed artifact and falsifying changes with a test expected to fail before claiming success.

How to structure a bug fix workflow for autonomous coding agents?▼

Use a repair loop: reproduce the failure on live truth without editing source, write a minimal failing regression test, fix the flaw class at the shared seam, verify on the real path, and get an independent grade before landing.

What files does the optimus boot sequence load?▼

It reads `.hydraAgent/policies/backs-invariants.yaml` for the invariant map and `.hydraAgent/playbooks/dev-mode-elite-build.yaml` for the environment play, then invokes the `the_path` and `elite_build_understanding` skills.

Can the same model write and grade its own code fix?▼

No. The builder is never the grader: a different model family must pass the change before it lands. This prevents self-confirming evaluations where the author overlooks its own flaws.

When should I not rely on mocks in regression tests?▼

Never mock the seam under test; mock only the external leaf dependency. A test that passes against a mock of the thing being fixed proves nothing about real behavior.