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 skills/t-rav/hydraflow/hf.issuenpx skills add T-rav/hydraflow --skill hf.issuegit 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.issue)<a href="https://agentmods.dev/skills/t-rav/hydraflow/hf.issue"><img src="https://agentmods.dev/badge/skills/t-rav/hydraflow/hf.issue.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.00008 | $0.01414 |
| Opus 5 | $0.00004 | $0.00707 |
| Sonnet 5 | $0.00002 | $0.00283 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
hf.issue 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a GitHub Issue
Take a rough description from the user, research the relevant codebase, and create a well-structured GitHub issue with full context, file references, and acceptance criteria.
Usage
/gh-issue add a Stop hook that checks for Langfuse tracing in new LLM code
/gh-issue the tasks service Google Drive auth flow doesn't handle token refresh
$ARGUMENTS contains the rough issue description from the user.
If $ARGUMENTS is empty, ask the user to describe the issue.
Instructions
Phase 0: Resolve Configuration
Before doing anything else, resolve these three values. Use the EXACT fallback logic below — do NOT pass empty strings to gh issue create:
- REPO: Run
echo "$HYDRAFLOW_GITHUB_REPO". If the output is empty, rungit remote get-url originand extract theowner/reposlug (striphttps://github.com/prefix and.gitsuffix). - ASSIGNEE: Run
echo "$HYDRAFLOW_GITHUB_ASSIGNEE". If the output is empty, extract the owner from the repo slug (the part before/). - LABEL: Use
hydraflow-find(the canonical label for discovery-stage issues).
Phase 1: Understand the Request
Parse $ARGUMENTS to understand what the user wants filed as an issue. Identify:
- What area of the codebase is involved
- What the problem or feature request is
- Any specific services, files, or patterns mentioned
Epic detection: If the user mentions "epic", "break into sub-issues", "multiple parts", or describes a large multi-component feature, treat this as an EPIC:
- Prefix the title with
[Epic] - Use the
hydraflow-epiclabel (NOThydraflow-find— the parent epic is a tracking issue, not implementable) - Create sub-issues separately, each WITH the
hydraflow-findlabel - Link sub-issues in the epic body with checkboxes:
- [ ] #123 — title
Phase 2: Research the Codebase
Before writing the issue, explore the codebase to gather concrete context:
- Use Grep/Glob/Read to find the relevant files, services, and patterns
- Understand the current state of the code related to the issue
- Identify specific file paths, function names, and line numbers
- Check for existing related patterns or prior art in the codebase
- Look at how similar things are already done elsewhere
- If the issue involves UI changes:
- Explore
ui/src/components/for existing component patterns that overlap or could be reused - Check
ui/src/constants.jsfor shared constants (e.g.,PIPELINE_STAGES,ACTIVE_STATUSES) - Check
ui/src/types.jsfor shared type definitions - Check
ui/src/theme.jsfor the design system's color tokens and spacing values - Note the styling approach used in similar components (inline styles, CSS modules, etc.)
- Explore
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 · 167 lines · 8 tokens per session scan A 6dbb9f5f452f
hf.issue is a skill published in the GitHub repository T-rav/hydraflow (5 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 1,414 once invoked, about $0.0000 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.
Other skills, from other repositories
develop
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never…
test
Run /test to write a test suite for code you just built or changed, after implementing a feature, route, or fix. Targets uncommitted changes automatically, reads test preferences.json for your framework (asks and saves it if absent), and picks the right strategy per file: happy path, edge cases, error states…
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
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…