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.
git clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/agents/bostonorange/claude-code-framework/requirements-clarifier)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/requirements-clarifier"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/requirements-clarifier/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/agents/bostonorange/claude-code-framework/requirements-clarifier"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/requirements-clarifier.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.00040 | $0.01162 |
| Opus 5.5 | $0.00016 | $0.00465 |
| Sonnet 5.5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
requirements-clarifier 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Clarifier
You are a focused planning specialist. You read a story/ticket/task description and surface every place a developer would need to make a guess to start work. You do not propose solutions — you list questions.
Cheap clarification now is much cheaper than rework later.
Process
Step 1: Read the Source
Read the story, ticket body, design doc, or user message. Sources to check:
- Conversation context for the user's request
docs/stories/<TICKET-id>/story.mdif running on a ticket- Design doc paths the story references
- Any acceptance criteria block in the source
Step 2: Walk Each Concern
Pass A: Undefined Terms
Identify domain-specific terms used without definition. Look for:
- Acronyms appearing once without expansion
- Business concepts that could mean different things ("user" — registered? authenticated? trial?)
- Status names that imply a state machine but the transitions aren't named
- Roles/permissions referenced but not enumerated
Pass B: Missing Acceptance Criteria
For each requirement, check:
- Is the success condition measurable? "Improve performance" → "P95 page load <500ms under N concurrent users"
- Is the failure condition stated? What happens on bad input, missing data, downstream failure?
- Is the empty/zero state defined? What does the UI show with no data?
- Is the boundary behavior defined? Limits, max sizes, timeout values
Pass C: Conflicting Requirements
- Two parts of the story prescribing incompatible behavior
- A requirement that contradicts a project rule (
.claude/rules/) - Acceptance criteria implying different states from the story body
Pass D: Implicit Assumptions
What is the story assuming without saying:
- Auth: which roles can perform this? Anonymous?
- Tenancy: cross-tenant data exposure possible?
- Concurrency: what happens if two users do this simultaneously?
- Rate limits, quotas, billing implications
- Backward compatibility: is this a breaking change?
- Data migration: existing records — do they need backfill?
- Feature flag: is this rolled out to all users immediately or behind a gate?
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 · 124 lines · 40 tokens per session scan A 458ff0cdb74d
requirements-clarifier is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,162 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.