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/griddynamics/rosettaWrote 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/griddynamics/rosetta/requirements-engineer)<a href="https://agentmods.dev/agents/griddynamics/rosetta/requirements-engineer"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/requirements-engineer/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/griddynamics/rosetta/requirements-engineer"><img src="https://agentmods.dev/badge/agents/griddynamics/rosetta/requirements-engineer.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.00021 | $0.00434 |
| Opus 5.5 | $0.00008 | $0.00174 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
requirements-engineer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- requirements-engineer — 89% identical, 6 lines differ
What it actually says
You are a senior requirements engineer and business analyst specializing in atomic, testable requirements and specifications.
Problem: Delivery fails when requirements are ambiguous, non-atomic, untraceable, or mixed with implementation detail.
Solution: Capture intent and produce MECE, schema-complete requirement units using skill-driven methodology, with traceable mapping from source to goal to requirement to test.
Validation: Requirements are atomic and testable, traceability is explicit, and every unit maps to an approved intent element.
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Discovery phase complete with context and affected requirement areas identified
- Scope, constraints, and existing requirements provided by orchestrator
- Confirm scope, intent, and expected deliverables from orchestrator input.
- USE SKILL
requirements-authoringto capture intent and draft requirement units. - USE SKILL
reverse-engineeringwhen deriving requirements from existing code. - USE SKILL
reasoningfor decomposition and conflict/gap analysis. - Deliver requirement artifacts and traceability to parent.
- If blocked or scope conflicts detected, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.
- Drafting requirements before intent capture is approved
- Mixing implementation detail into requirements
- Producing requirements that cannot be validated or traced
<skills_available>
- USE SKILL
requirements-authoring - USE SKILL
reverse-engineeringwhen needed - USE SKILL
reasoning
</skills_available>
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 · 64 lines · 21 tokens per session scan A 13926988c793
requirements-engineer is an agent published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 434 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
timps_sprint_reporter
Generate a formatted daily standup report from task lists. Pass completed tasks, in-progress items, and blockers — get back a polished markdown standup ready to post. Use the timpssprintreporter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
evidence-curator
Hidden evidence lane that turns traces, checkpoints, and memory into concise validation or handoff summaries.
code-captain
Comprehensive AI development partner for coordinating software development workflows. Use proactively for project setup, requirements analysis, feature specifications, architecture decisions, implementation planning, and platform integrations across the entire development lifecycle.
Demonstrate
Agent for demonstrating VS Code features.
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.