Hermes runtime ONLY — the Nirvana-OS bridge for Hermes Agent. Every other runtime loads the first-class nirvana skill instead and must ignore this one. Lists and inspects the user's Nirvana-OS businesses (empresas) and squads and routes production briefs to the harness orchestrator via nrv dispatch. Trigger when the…
Autonomous generalist Antigravity CLI (agy) executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Autonomous generalist Claude Code executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Autonomous generalist Codex CLI executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Autonomous generalist Grok Build CLI executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Autonomous generalist Kimi Code CLI executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Autonomous generalist Pi Coding Agent executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Independent Gauntlet judge for Antigravity CLI (agy), invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one…
Independent Gauntlet judge for Claude Code, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…
Independent Gauntlet judge for Codex CLI, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…
Independent Gauntlet judge for Grok Build CLI, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json…
Independent Gauntlet judge for Kimi Code CLI, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…
Independent Gauntlet judge for Pi Coding Agent, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json…
Business lifecycle skill (DOMAIN-AGNOSTIC). Creates, lists, inspects, validates, and migrates businesses — autonomous multi-agent organizations — following the Business Protocol v2 (v1 businesses still load unchanged). Works for ANY domain: marketing, healthcare, engineering, legal, real-estate, gaming, foodtech…
Nirvana-OS orchestrator: routes a brief across the user's own library of businesses, squads and mind-clones, dispatches the best combination, and gates the result before delivery. Use when the user asks for a concrete artifact (book, video, report, design, code, campaign, any deliverable) in a machine where Nirvana-OS…
Layer 2 of the dispatch-quality plan. Runs between targetplancommitted and the actual dispatch. Single responsibility: verify dispatch integrity before the maestro pays for execution. Reads: the brief (verbatim) the target plan (mind-clones / squads / businesses chosen) the system prompt(s) about to be sent to the…
Squad lifecycle skill. Use when asked to create, validate, inspect, list, or migrate squads — portable AI agent teams with workflows. Triggers on: create squad, list squads, inspect squad, validate squad, migrate squad, adapters. For EXECUTION of production briefs ('use the squad X', 'orquestre via squad', 'rode via…
Invoke whenever the user says "ative o squad X", "active squad X", "instale as dependências de X", "set up X", or asks to prepare a squad for use. This agent is the single entry point for activation + dependency install. It reads the squad's dependencies.yaml, summarizes scope, asks for consent on heavy items, runs…
Nirvana-OS entry point: the user's own operating system of businesses (empresas), squads and mind-clones. Use it to list or inspect them ('quais são minhas empresas', 'quais squads eu tenho', 'what businesses/squads do I have', 'liste minhas empresas', 'quais mind-clones eu tenho', 'o que o nirvana pode fazer')…
Multi-agent squad orchestrator. Use when asked to create, validate, run, inspect, migrate, or manage squads — portable AI agent teams with workflows. Triggers on: squad, squads, multi-agent, workflow, create squad, run squad, list squads, activate squad, validate squad, migrate squad, adapters.
★not rated 10 5mo agoC68 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: