Refine Requirement or Issue

A guided way to expand a software issue into a clearer work plan, including what must be true when the work is finished, technical details, unusual cases, and non-functional requirements such as speed or security.

In plain words
What is it for?
It helps refine an existing GitHub issue, add testable acceptance criteria, record dependencies and risks, and suggest information for estimating the work.
Why use it?
It removes guesswork from vague issue descriptions and gives developers and reviewers a shared understanding of the expected result.

Agent

Install

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.

agentmods
npx agentmods add agents/co-native-ab/graphdo-ts/refine-issue
Clone the repo
git clone --depth 1 https://github.com/co-native-ab/graphdo-ts
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 298 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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 $0.00027 $0.00298
Opus 5 $0.00014 $0.00149
Sonnet 5 $0.00005 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 2d ago against content hash 2db9cda57b0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Refine Requirement or 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 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.

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.

Origin

This is a copy

88% identical to refine-issue — 33 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/refine-issue.agent.md · 49 lines

What it actually says

Refine Requirement or Issue Chat Mode

When activated, this mode allows GitHub Copilot to analyze an existing issue and enrich it with structured details including:

  • Detailed description with context and background
  • Acceptance criteria in a testable format
  • Technical considerations and dependencies
  • Potential edge cases and risks
  • Expected NFR (Non-Functional Requirements)

Steps to Run

  1. Read the issue description and understand the context.
  2. Modify the issue description to include more details.
  3. Add acceptance criteria in a testable format.
  4. Include technical considerations and dependencies.
  5. Add potential edge cases and risks.
  6. Provide suggestions for effort estimation.
  7. Review the refined requirement and make any necessary adjustments.

Usage

To activate Requirement Refinement mode:

  1. Refer an existing issue in your prompt as refine <issue_URL>
  2. Use the mode: refine-issue

Output

Copilot will modify the issue description and add structured details to it.

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. 2d ago First seen · 49 lines · 27 tokens per session scan A 2db9cda57b0b

Subscribe to this mod's changes

Refine Requirement or Issue is an agent published in the GitHub repository co-native-ab/graphdo-ts (1 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 298 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to refine-issue, differing in 33 lines, and is treated as a copy.