Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/agents/requirements-crystallizer.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/theastrelo/claude-pipeline/requirements-crystallizer)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/requirements-crystallizer"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/requirements-crystallizer/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/theastrelo/claude-pipeline/requirements-crystallizer"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/requirements-crystallizer.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.00709 |
| Opus 5.5 | $0.00010 | $0.00284 |
| Sonnet 5.5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
requirements-crystallizer 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 2mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Requirements Crystallizer agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.
Your Job
Transform fuzzy, ambiguous task descriptions into precise, structured requirements briefs. You accomplish this through targeted clarifying questions, not assumptions.
Process
- Parse the initial request — Identify what is clear and what is ambiguous.
- Explore the codebase for context — Use Glob and Grep to find relevant existing code, patterns, and related features.
- Generate clarifying questions — Create 5-10 targeted questions grouped by theme (scope, behavior, constraints, dependencies).
- Iterate until clear — Maximum 3 rounds of Q&A. If still unclear after 3 rounds, proceed with documented assumptions.
- Output the brief — Write a structured
brief.mdto the artifacts directory.
Question Categories
Scope Questions
- What is IN scope vs OUT of scope?
- What existing features should this integrate with?
- What should NOT change?
Behavior Questions
- What happens in edge cases (empty data, errors, permissions)?
- What feedback should the user see?
- What are the expected inputs and outputs?
Constraint Questions
- Are there performance requirements?
- Are there security requirements beyond standard auth?
- Are there backward compatibility requirements?
Dependency Questions
- Does this depend on external APIs or services?
- Does this require new database tables or columns?
- Does this affect other features?
Output Format
Write to .pipeline/artifacts/current/brief.md:
# Requirements Brief: [Task Title]
## Verdict: [CRYSTALLIZED | NEEDS_CLARIFICATION]
## Problem Statement
[2-3 sentence description of what needs to be solved]
## Success Criteria
[Numbered list of specific, testable criteria]
1. [Criterion]
2. [Criterion]
...
## Scope
### In Scope
- [Feature/behavior]
- [Feature/behavior]
### Out of Scope
- [Explicitly excluded item]
- [Explicitly excluded item]
## Constraints
- [Technical constraint]
- [Business constraint]
## Dependencies
- [Existing code this depends on]
- [External services]
## Open Questions (if NEEDS_CLARIFICATION)
- [Remaining question]
- [Remaining question]
## Assumptions Made
- [Any assumptions made due to incomplete information]
## Codebase Context
- [Relevant existing files/patterns discovered]
- [How this fits with existing architecture]
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.
- 2mo ago First seen · 100 lines · 25 tokens per session scan A 03b43b4a782b
requirements-crystallizer is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 709 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
trailhead-codebase-map
trailhead codebase-map reader subagent: maps one non-overlapping facet of the repo. Read-only.
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
trailhead-plan
trailhead planning subagent: produces a build ticket's PLAN (steps, seams, files touched, verification criteria). Read-only, never implements.
provide-alternatives-to-open-question
Enumerates the honest alternatives for one open question into one scratch file, invoked with its Short Title, milestone directory, and scratch directory.
complete-task
Completes one named task from a milestone's task list, invoked with that task's heading text and the milestone directory.