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 skills add tomzx/agents --skill qualify-issuegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/qualify-issue)<a href="https://agentmods.dev/skills/tomzx/agents/qualify-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/qualify-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.
<a href="https://agentmods.dev/skills/tomzx/agents/qualify-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/qualify-issue.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.01596 |
| Opus 5 | $0.00013 | $0.00798 |
| Sonnet 5 | $0.00005 | $0.00319 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
qualify-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 6d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qualify Issue
Takes an externally submitted GitHub issue (feature request or bug report) and drives a structured Q&A loop with the reporter until the issue contains enough information to proceed to /create-requirements.
Assumes review-issue has already been run and identified what is missing.
This skill owns the iterative clarification loop. It stops when the issue is fully qualified or the reporter is unresponsive.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the issue from
$ISSUE_NUMBER(and$REPO). ghCLI authenticated with write access to the target repository- Issue URL or number (
$1), and optionally repository inowner/repoformat ($2) - Read any files present under
.sdlc/context/and apply any artifact style rules found there
Skill attribution (GitHub)
Before posting any comment with gh, read ../github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = qualify-issue.
Workflow
Fetch issue + comment history
|
v
Identify open questions
|
v
All answered?
/ \
Yes No
| |
v v
Update issue Post questions
body + signal as comment
"qualified" |
v
Wait for reporter
(skill stops here)
|
v
Re-invoke when
replies arrive
Steps
1. Fetch the issue and full comment history
ghx issue view $1 [--repo $2] --comments
Extract:
- Issue type (bug / feature request)
- What is already known (background, version, steps, ACs, etc.)
- What is still missing or ambiguous
- Any prior clarification comments and their answers
2. Identify open questions
Using the review-issue checklist as the standard, determine what information is still needed:
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.
- 6d ago First seen · 196 lines · 25 tokens per session scan A 1ad20927af07
qualify-issue is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,596 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.