agent-rules: Command for Claude Code

.agents/commands/HYDRATE-GH-ISSUE.md

HYDRATE-GH-ISSUE is a command for Claude Code from dep/agent-rules. It costs 0 tokens per session (137 once invoked), scanned A, original, MIT.

A command for preparing detailed GitHub issue descriptions from a request. GitHub Issues are project records used to track bugs, tasks, and feature requests.

In plain words
What is it for?
Use it to create a new issue or update an existing one when the request needs clarification and a well-structured description.
Why use it?
It turns incomplete issue details into a clearer statement of requirements, expected behavior, and context.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents).

This is dep/agent-rules's own configuration. It tells Claude Code how to work on agent-rules itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-rules configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dep/agent-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dep/agent-rules/main/.agents/commands/HYDRATE-GH-ISSUE.md
Clone the repo
git clone --depth 1 https://github.com/dep/agent-rules

Made for: Claude Code.

Wrote 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.

agentmods badge for HYDRATE-GH-ISSUE

README.md
[![agentmods](https://agentmods.dev/badge/commands/dep/agent-rules/hydrate-gh-issue/github.svg)](https://agentmods.dev/commands/dep/agent-rules/hydrate-gh-issue)
Your own site
<a href="https://agentmods.dev/commands/dep/agent-rules/hydrate-gh-issue"><img src="https://agentmods.dev/badge/commands/dep/agent-rules/hydrate-gh-issue/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.

agentmods 80×15 button for HYDRATE-GH-ISSUE

Your own site · 80×15
<a href="https://agentmods.dev/commands/dep/agent-rules/hydrate-gh-issue"><img src="https://agentmods.dev/badge/commands/dep/agent-rules/hydrate-gh-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00137
Opus 5.5 $0.00000 $0.00055
Sonnet 5.5 $0.00000 $0.00027
Haiku 4.5 $0.00000 $0.00014

Measured 1mo ago against content hash 63285978c14f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

HYDRATE-GH-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 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.

.agents/commands/HYDRATE-GH-ISSUE.md · 12 lines

What it actually says

Hydrate Github Issue Details v1.0.0

Overview

Use the Github MCP server (or the Github (gh) skill) to create a description for the provided Github issue (if a URL was provided, update the issue, otherwise create a new issue).

This should capture the high level requirements and details of the request.

This should be a detailed description of the request, including the expected behavior, and any relevant context without getting into the details of the implementation with code.

One-at-a-time, ask for clarification on any details you are not 100% sure about. The options should be listed as A, B, C, to make choosing easier.

Changes

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.

  1. 1mo ago First seen · 12 lines · 0 tokens per session scan A 63285978c14f

Subscribe to this mod's changes

HYDRATE-GH-ISSUE is a command published in the GitHub repository dep/agent-rules (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 137 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-30.