Borrowing it
Nothing to install: this file belongs to T-rav/hydraflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/T-rav/hydraflow/staging/.codex/skills/hf.audit-code/SKILL.mdgit 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/skills/t-rav/hydraflow/hf.audit-code)<a href="https://agentmods.dev/skills/t-rav/hydraflow/hf.audit-code"><img src="https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.audit-code/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/skills/t-rav/hydraflow/hf.audit-code"><img src="https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.audit-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00007 | $0.03928 |
| Opus 5.5 | $0.00003 | $0.01571 |
| Sonnet 5.5 | $0.00001 | $0.00786 |
| Haiku 4.5 | $0.00001 | $0.00393 |
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 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.
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 — 357 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, and architectural problems. 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-planas 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: Complexity & duplication — Finds overly complex functions, duplicated logic, and DRY violations.
- 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.
-
Wait for all agents to complete.
-
After all finish, run
gh issue list --repo $REPO --label $LABEL --state open --search "code 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.
- 1mo ago First seen · 357 lines · 7 tokens per session scan A 1415ca494b98
hf.audit-code is a skill published in the GitHub repository T-rav/hydraflow (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 7 tokens to every session and 3,928 once invoked, about $0.0000 per session on Opus 5.5. 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 skills, from other repositories
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…
feedback-resolution
Address PR review feedback through surgical fixes traceable to specific comments, apply the Boy Scout Rule only to already-modified files (separate improve: commits), recover context by code snippet rather than line number, and enforce pushback only when factually incorrect, test-breaking, or CLAUDE.md-violating. Use…
holdout-validation
Cross-reference agent self-review claims and evidence-bundle entries against actual file state using hidden holdout scenarios, producing P1/P2/P3 findings mapped to visible acceptance criteria only. Checks that every expected value in the tests has the source the bundle claims and that every risk-map row has a…
code-quality-principles
Enforce code quality through the Boy Scout Rule (leave code better than found), secret-free commits, production-ready code (no TODOs, console.log, mocks, or commented code), and self-review against an atomic-commits checklist. Use when writing, modifying, or reviewing code. This skill MUST be consulted because…
code-review-methodology
Conduct two-stage code review: Stage 1 verifies spec compliance (criterion-to-code mapping), Stage 2 evaluates security, correctness, performance, and maintainability across 6 parallel facets with P1/P2/P3 synthesis and deduplication by file:line. For the Tests facet the reviewer derives expected behavior from the…
pr-lifecycle
Reference document describing PR lifecycle: pre-flight gates (4 conditions), verification gate (5 conditions), body structure (from templates/pr-body.md), reviewer-suggestion algorithm (CODEOWNERS → file expertise → recent activity → workload balance), and finding-ledger merge prerequisite. Reference only (policy…