Borrowing it
Nothing to install: this file belongs to severity1/claude-agent-sdk-go. 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/severity1/claude-agent-sdk-go/main/.claude/commands/qualify.mdgit clone --depth 1 https://github.com/severity1/claude-agent-sdk-goWrote 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/commands/severity1/claude-agent-sdk-go/qualify)<a href="https://agentmods.dev/commands/severity1/claude-agent-sdk-go/qualify"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/qualify/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/commands/severity1/claude-agent-sdk-go/qualify"><img src="https://agentmods.dev/badge/commands/severity1/claude-agent-sdk-go/qualify.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.00017 | $0.01686 |
| Opus 5.5 | $0.00007 | $0.00674 |
| Sonnet 5.5 | $0.00003 | $0.00337 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
qualify 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://platform.claude.com/docs/en/agent-sdk/python.md How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue and PR Qualification
Validate issue/PR #$ARGUMENTS for correctness, completeness, and Python SDK alignment. Produces a verdict report that feeds into /tdd.
Phase 1: Identification & Context Gathering
Determine what #$ARGUMENTS is and find its linked counterpart:
- Check if it is an issue - Run
gh issue view $ARGUMENTS --json number,title,body,state,labels,comments - Check if it is a PR - Run
gh pr view $ARGUMENTS --json number,title,body,state,files,additions,deletions,commits,comments,headRefName - Find the linked counterpart:
- If PR: extract linked issue from body (
Closes #N,Fixes #N,Issue #N,(Issue #N)) and fetch it - If issue: search for linked PRs via
gh pr list --search "issue #$ARGUMENTS"and check open PRs referencing it
- If PR: extract linked issue from body (
- Fetch all comments on both the issue and PR (if both exist) for additional context
Display a summary:
Context for #$ARGUMENTS
-----------------------
Issue: #<number> - <title> (<state>)
PR: #<number> - <title> (<state>) [or "None found"]
Phase 2: Issue Validation
Assess whether the issue is well-defined and ready for implementation:
- Check issue structure - Does the body contain:
- Clear description of the problem or feature
- Reproduction steps (for bugs)
- Proposed Implementation section
- Files to Modify section
- Example Usage (if applicable)
- Read all comments - Look for scope changes, decisions, or additional requirements added after filing
- Check labels - Confirm categorization (bug, enhancement, good first issue, etc.)
- Extract requirements - Build a numbered list of acceptance criteria from the issue body and comments. Include both explicit requirements and implied ones.
Output the requirements list - this feeds directly into /tdd Phase 2:
Requirements for #$ARGUMENTS
-----------------------------
1. <requirement>
2. <requirement>
...
If the issue is missing critical information: Note the gaps but continue - the verdict will reflect them.
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 · 162 lines · 17 tokens per session scan A 0af421143328
qualify is a command published in the GitHub repository severity1/claude-agent-sdk-go (176 stars, last pushed 23d ago), licensed MIT. It adds 17 tokens to every session and 1,686 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
full-review
Orchestrate comprehensive multi-dimensional code review using specialized review agents across architecture, security, performance, testing, and best practices.
pr-enhance
Enhance a pull request with a generated description, review checklist, risk assessment, and test coverage report.
tech-debt
Analyze and remediate technical debt — inventory debt items, score by impact, and produce a prioritized remediation plan with estimated effort.
team-review
Launch a multi-reviewer parallel code review with specialized review dimensions.
review
Review the code changes and provide detailed feedback.