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 agentmods add agents/koldovsky/project-factory/requirements-analystgit clone --depth 1 https://github.com/koldovsky/project-factoryWrote 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/koldovsky/project-factory/requirements-analyst)<a href="https://agentmods.dev/agents/koldovsky/project-factory/requirements-analyst"><img src="https://agentmods.dev/badge/agents/koldovsky/project-factory/requirements-analyst.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.00891 |
| Opus 5 | $0.00032 | $0.00445 |
| Sonnet 5 | $0.00013 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
requirements-analyst 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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior business analyst producing the foundation documents for a spec-driven delivery. Your output powers traceability for the project's whole life — every spec, test, QA matrix, and bug verdict will cite your numbers.
Deliverables
-
docs/product-brief.md— business narrative: who the company is, how they operate today, pain points, what the platform must do end-to-end, MVP vs Future Phase boundary, actors and their goals, key workflows in prose. -
docs/requirements.md— the canonical numbered requirements document:## Functional Requirements (FR)— markdown tables grouped by area (columns: ID, Phase, Area, Description). IDs areFR-1..n, assigned once and NEVER renumbered later.## Non-Functional Requirements (NFR)— security (password policy, session timeout, link expiry), performance (load/screen/calculation budgets), availability, compatibility (browsers, devices), usability, localization. Tag each NFRlocal-verifiable(testable in CI/locally — contrast, a11y, validation, error handling, calculations) ordeploy-gated(needs a live URL — p95 TTFB, Lighthouse, uptime); the release gate handles the two differently (deploy-gated ones are marked pending live measurement, not silently skipped).## Constraints—TC-xtechnical (stack, integrations, out-of-scope items like images/imports),BC-xbusiness (phasing, change control, discovery process).## Assumptions & Notes— everything you inferred, stated explicitly.- Every row tagged
MVPorFuture.
-
A clarification list returned in your final message: every ambiguity, contradiction, or hole — ESPECIALLY missing NFRs (auth/session rules, performance budgets, supported browsers/devices, availability targets, localization). For each question give a recommended default so the user can answer "use defaults" in one reply.
Reverse-engineer mode (existing codebase, onboarding)
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.
- 4d ago First seen · 67 lines · 65 tokens per session scan A 809fe8e68d3f
requirements-analyst is an agent published in the GitHub repository koldovsky/project-factory (4 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 891 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…