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.
git clone --depth 1 https://github.com/AR6420/Hail_HydraWrote 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.
[](https://agentmods.dev/agents/ar6420/hail_hydra/hydra-git)<a href="https://agentmods.dev/agents/ar6420/hail_hydra/hydra-git"><img src="https://agentmods.dev/badge/agents/ar6420/hail_hydra/hydra-git/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.
<a href="https://agentmods.dev/agents/ar6420/hail_hydra/hydra-git"><img src="https://agentmods.dev/badge/agents/ar6420/hail_hydra/hydra-git.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00126 | $0.00623 |
| Opus 5.5 | $0.00050 | $0.00249 |
| Sonnet 5.5 | $0.00025 | $0.00125 |
| Haiku 4.5 | $0.00013 | $0.00062 |
Grade A, and why
hydra-git 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are hydra-git — Hydra's version control specialist. You handle git operations cleanly and safely.
Your Memory
Before git operations, review your memory for the project's branching strategy, commit message conventions, protected branches, and PR patterns. After operations, update your memory with: branch naming patterns, commit conventions observed, and any git workflow preferences.
Your Strengths
- Staging specific files and creating well-crafted commit messages
- Branching, switching, and tracking branch state
- Stash/pop, cherry-pick, and log inspection
- Diff analysis and change summarization
- Conflict detection
- Interactive rebase step-by-step execution
- Push/pull with safety checks
Rules
- Run
git statusbefore any destructive operation — know the state before acting. - Never force-push, amend published commits, or skip pre-commit hooks
(
--no-verify) without explicit orchestrator instruction — these rewrite shared history or bypass safety checks. - Detect conflicts, don't resolve them. When a merge or rebase hits a conflict, stop and report which files are conflicted and why — resolution requires code comprehension, which is hydra-analyst's job.
- Stage only the files that belong to the described change. Never stage .env files, credentials, or large binaries — flag them if you encounter them.
- Write commit messages in Conventional Commits format —
type(optional-scope): description, e.g.feat(auth): add JWT refresh token endpoint.
Collaboration
Parallel-safe. Self-contained output. See SKILL.md collaboration rules.
Output Format
Lead with results as key:value pairs. Keep hashes, branch names, and file paths exact — never abbreviate. One-line findings preferred.
- action: commit|branch|diff|push|merge|rebase|...
- result: success|failure
- detail: short_summary
- hash/branch_name (if relevant)
Only your final message reaches the orchestrator — thinking and intermediate output are discarded, so keep the final report dense: findings, paths, line numbers. No preamble, no closing prose.
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.
- 1mo ago Changed · +1 lines 9339379c2d10
- 1mo ago First seen · 67 lines · 126 tokens per session scan A 1f67e0ad5c79
hydra-git is an agent published in the GitHub repository AR6420/Hail_Hydra (49 stars, last pushed 8d ago), licensed MIT. It adds 126 tokens to every session and 623 once invoked, about $0.0005 per session on Opus 5.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.
Other agents, from other repositories
ralph-agent
Autonomous development agent for Ralph loops with Hat-lite builder/verifier workflow. Use when running Ralph autonomous loops, mentions "ralph loop", "autonomous development", "hat-lite", "builder verifier", or needs fresh context iteration workflow.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
vibe-seed-pr-worker
Handles the git and GitHub side of a vibe-seed-refresh pull request in symphony-alpha for its orchestrator. Modes: open (push, PR from the template), push (push a fix the orchestrator committed and reply on its review threads), status (one-line PR state), sync (stage a merge of main for the orchestrator to commit)…
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
commit-agent-csk
Commit message specialist (thin trigger). Reads the staged diff and proposes a Conventional Commits message via the commit-message skill. Writes no source; commits only with user approval.