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-testsgit clone --depth 1 https://github.com/T-rav/hydraflowWrote 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/commands/t-rav/hydraflow/hf.audit-tests)<a href="https://agentmods.dev/commands/t-rav/hydraflow/hf.audit-tests"><img src="https://agentmods.dev/badge/commands/t-rav/hydraflow/hf.audit-tests.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.04909 |
| Opus 5 | $0.00000 | $0.02455 |
| Sonnet 5 | $0.00000 | $0.00982 |
| Haiku 4.5 | $0.00000 | $0.00491 |
Grade A, and why
hf.audit-tests 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 4d 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Audit
Run a comprehensive test quality audit across the entire repo. Analyzes test naming, structure, hygiene, factory usage, fluent builder patterns, anti-patterns, coverage gaps, and flaky patterns. 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 test files:
**/test_*.py,**/tests/conftest.py,**/tests/helpers.py - Exclude
.venv/,venv/,__pycache__/,node_modules/ - Also find all UI test files:
ui/src/**/*.test.jsx,ui/src/**/*.test.js - Count total test files and identify the test helper infrastructure
- Use Glob to find all test files:
-
Launch agents in parallel using
Taskwithrun_in_background: trueandsubagent_type: "general-purpose":- Agent 1: Test naming, structure & method size — Checks naming conventions, 3As structure, single responsibility, small test methods, and organization.
- Agent 2: Anti-patterns, hygiene & flaky tests — Detects over-mocking, weak assertions, duplicate helpers, flaky patterns, and test isolation issues.
- Agent 3: Factory/fixture gaps, builder enforcement & coverage — Finds missing factories, enforces fluent builder pattern, checks coverage gaps, and missing edge case tests.
-
Wait for all agents to complete.
-
After all finish, run
gh issue list --repo $REPO --label $LABEL --state open --search "test quality" --limit 200to show the user a final summary of all issues created.
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.
- 4d ago First seen · 419 lines · 0 tokens per session scan A bdfbea0ba34b
hf.audit-tests is a command published in the GitHub repository T-rav/hydraflow (5 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,909 tokens. 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.
Other commands, from other repositories
start
Start work on a GitHub issue. Assigns issue, creates branch, decomposes tasks from acceptance criteria, and guides implementation with autonomous execution.
address
Address PR review feedback systematically. Categorizes feedback, implements surgical fixes, verifies changes, and re-requests review.
pr
Create a pull request with full code review, quality gates, comprehension report, and reviewer suggestions. Runs parallel agent review before PR creation.
goal
Manage FlowGoal completion contracts — create, inspect, evaluate, pause/resume/clear, history. Use when starting a goal-driven task, when checking active-goal state, or when finalizing the verdict after evidence is collected. Captures acceptance criteria with verification commands, runs deterministic checks, and…
gh-release
Create a new release for the marketplace or a specific plugin.
baseline
Build the full documentation package from evidence. Inventories sources, models the project, resolves material gaps, drafts the 21 internal documents in dependency waves, then derives the 2 public documents from approved claims only.