hydra-review

hydra-review is a skill for Codex from azixxxxx/Hydra. It costs 36 tokens per session (792 once invoked), scanned A, original, MIT.

A skill for getting an independent, read-only review of code, architecture, tests, or a pre-merge change from a specified model. Findings must be supported by evidence from the repository.

In plain words
What is it for?
Reviewing changes before merge, checking architecture and tests, and reporting findings with paths, lines, severity, claims, and evidence.
Why use it?
It adds a separate review of possible defects while requiring reproducible support instead of accepting unsupported claims.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Reviewing changes before merge, checking architecture and tests, and reporting findings with paths, lines, severity, claims, and evidence.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/azixxxxx/hydra/hydra-review
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.

Any agent
npx skills add azixxxxx/Hydra --skill hydra-review
Clone the repo
git clone --depth 1 https://github.com/azixxxxx/Hydra

Made for: 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 hydra-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/azixxxxx/hydra/hydra-review/github.svg)](https://agentmods.dev/skills/azixxxxx/hydra/hydra-review)
Your own site
<a href="https://agentmods.dev/skills/azixxxxx/hydra/hydra-review"><img src="https://agentmods.dev/badge/skills/azixxxxx/hydra/hydra-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hydra-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/azixxxxx/hydra/hydra-review"><img src="https://agentmods.dev/badge/skills/azixxxxx/hydra/hydra-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 792 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00036 $0.00792
Opus 5 $0.00018 $0.00396
Sonnet 5 $0.00007 $0.00158
Haiku 4.5 $0.00004 $0.00079

Measured 11d ago against content hash 5bc3ace02c6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

hydra-review 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 11d 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.

plugins/hydra/skills/hydra-review/SKILL.md · 50 lines

How it starts

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

Hydra Review

Principle

Return only findings that survive local verification. A fluent model claim without reproducible repository evidence is not a finding.

Workflow

  1. Call hydra_preflight for the repository. Stop if authentication, provider routing, CLI capabilities, or platform checks fail.

  2. Call hydra_budget with {"action":"status"}. Select Sonnet high for normal review. Select Opus xhigh for critical risk, architecture, or adversarial pre-merge review. Do not select Fable for ordinary code review and do not weaken a required review model to conserve allowance.

  3. Build the bounded context capsule below. Call hydra_start with accessMode: "analyze", strictModel: true, budgetIntent.priority: "quality-floor", the capsule plus one reviewer role-specific delta, and a bounded turn count.

  4. Require structured output with a findings array. Each item must contain:

    • path: repository-relative file path;
    • line: smallest relevant 1-based line number or null;
    • severity: critical, high, medium, or low;
    • claim: falsifiable description of the defect;
    • evidence: code path, state transition, command, or test that supports it;
    • uncertainty: explicit caveat or none;
    • suggestedCheck: narrow local verification step.
  5. Record the job ID, inspect hydra_status, and retrieve hydra_result only after a terminal state.

  6. For each candidate finding, open the cited code and its callers. Attempt to disprove the claim. Run the suggested focused test or another safe reproduction when practical.

  7. Drop any finding that local evidence does not support. Correct its severity when the stated impact or reach is unsupported.

  8. Report verified findings first, ordered by severity. Include the exact path and line, impact, evidence, and remaining uncertainty. If none survive, state that no verified findings were found and name the checks performed.

  9. Record taskType: "review", scope, accepted claims, rejected claims, false positives, testsBefore, testsAfter, patch verdict, and user verdict when known with hydra_record_outcome.

Read the full file on GitHub · 50 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. 11d ago First seen · 50 lines · 36 tokens per session scan A 5bc3ace02c6c

Subscribe to this mod's changes

hydra-review is a skill published in the GitHub repository azixxxxx/Hydra (0 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 792 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-31.

Related

Other skills, from other repositories

remarc

Manage Remarc session comments and contextual feedback. Use when the user mentions Remarc sessions, comments, handoff, triage, review, addressing, resolving, status updates, or summaries.

metedata/Remarc · 41 tokens

looper-qa

Use when a Looper-managed GitHub repo needs scheduled pre-merge QA — a PR carries the looper:qa label, the spec stage reaches looper:spec-ready, or the Looper reviewer loop requests an independent second pass. Runs the full QA cycle (Looper state probe → PR checkout → ffs code review → language-specific test suite →…

quangdang46/looper_rust · 125 tokens

codeck

Route explicit requests from a host coding agent to one or more locally configured AI executors through Codeck, attach Markdown or other project files, moderate cross-model consultation, expose disagreements, and synthesize traceable results. Use when the user explicitly names Codeck or asks to consult, compare, or…

isdou/codeck · 108 tokens

engine

Internal data-only review core invoked directly by /lens:review and by a programmatic orchestrator (matali) calling it as a compute-only step, to produce a review-findings JSON object from the session diff. Not user-invocable; returns data, writes nothing, never prompts.

ApurvBazari/claude-plugins · 61 tokens

review

Review the current session's changes against their spec and plan, adversarially verify the findings, and render an interactive review document. Use when the user wants to review what was just built before it ships, runs /lens:review, or asks to "review my changes / review this before I commit". Reviews Claude's own…

ApurvBazari/claude-plugins · 72 tokens

render-review

Internal pure-render entrypoint — given a review-findings object (plus optional prior findings, a diff ref, and intent), reconcile in-memory, assemble the review-model, and render the interactive HTML via walkthrough:render. Writes ONLY the output HTML; no lens state, no recompute, no task list. Invoked by an…

ApurvBazari/claude-plugins · 85 tokens