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.
npx agentmods add commands/t-rav/hydraflow/hf.audit-codegit clone --depth 1 https://github.com/T-rav/hydraflowWhat 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 | $0.00000 | $0.06814 |
| Opus 5 | $0.00000 | $0.03407 |
| Sonnet 5 | $0.00000 | $0.01363 |
| Haiku 4.5 | $0.00000 | $0.00681 |
Grade A, and why
hf.audit-code scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Do they have timeouts? (subprocess.run without timeout, asyncio without timeout) How it starts
The opening of the file, as written. The whole thing — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Audit
Run a comprehensive code quality audit across the entire repo. Dynamically analyzes source code for dead code, complexity, duplication, error handling gaps, type safety issues, class cohesion, and method size. Creates GitHub issues for findings so HydraFlow can process them.
Instructions
-
Resolve configuration before doing anything else:
- Run
echo "$HYDRAFLOW_GITHUB_REPO"— if set, use it as the target repo (e.g.,owner/repo). If empty, rungit remote get-url originand extract theowner/reposlug (striphttps://github.com/prefix and.gitsuffix). - Run
echo "$HYDRAFLOW_GITHUB_ASSIGNEE"— if set, use it as the issue assignee. If empty, extract the owner from the repo slug (the part before/). - Use
hydraflow-findas the label for created issues. - Store resolved values as
$REPO,$ASSIGNEE,$LABEL.
- Run
-
Discover project structure:
- Use Glob to find all
*.pysource files, excluding.venv/,venv/,__pycache__/,node_modules/,dist/,build/. - Separate into SOURCE files (production code) and TEST files (anything under
tests/or matchingtest_*.py). - Count total source files, total lines, and identify the main modules.
- Use Glob to find all
-
Launch agents in parallel using
Taskwithrun_in_background: trueandsubagent_type: "general-purpose":- Agent 1: Dead code & unused exports — Finds unreachable code, unused functions, unused imports, and stale modules.
- Agent 2: Method size, class cohesion & duplication — Enforces small methods, single-concept classes, and DRY.
- Agent 3: Error handling & robustness — Finds bare excepts, swallowed errors, missing error paths, and fragile patterns.
- Agent 4: Type safety & API consistency — Finds missing type annotations,
Anyoveruse, inconsistent return types, and public API gaps. - Agent 5: Convention drift & over-engineering — Reads
docs/wiki/gotchas.md(or CLAUDE.md fallback) at runtime and sweeps the codebase for documented avoided patterns plus over-engineering accumulation.
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.
- 2d ago First seen · 535 lines · 0 tokens per session scan A f47e57e543f5
hf.audit-code is a command published in the GitHub repository T-rav/hydraflow (5 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 6,814 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
gh-issue
Create a new GitHub issue following solution-agnostic principles.
gh-release
Create a new release for the marketplace or a specific plugin.
gh-merge
Merge an approved pull request with standardized settings.
gh-review
Review a pull request with proper branch checkout and convention checks.
ledger-plan
Generate implementation plan with backlog, milestones, and test plan constrained by decisions and risks.
ledger-update
Apply new learnings to the ledger and generate impact report showing what downstream artifacts need regeneration.