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 skills add emaraschio/cursor-commands --skill requirement-to-implementationgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/skills/emaraschio/cursor-commands/requirement-to-implementation)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/requirement-to-implementation"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/requirement-to-implementation/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/skills/emaraschio/cursor-commands/requirement-to-implementation"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/requirement-to-implementation.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.00068 | $0.01248 |
| Opus 5 | $0.00034 | $0.00624 |
| Sonnet 5 | $0.00014 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
requirement-to-implementation 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 6d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement to Implementation
Structured workflow that turns a requirement into verified, documented code. Every task (feature, bug fix, refactor, chore, or performance improvement) flows through the same phases.
Phase 0: Intake
Identify the requirement source and extract key information.
| Source | Action |
|---|---|
| Notion ticket | Use Notion MCP to fetch ticket details, acceptance criteria, and linked context |
| GitHub issue | Use gh issue view to pull title, body, labels, and linked PRs |
| Conversation | Extract the requirement from what the user described |
| Sentry issue | Use Sentry MCP to pull error details, stack traces, and affected users |
Produce a one-paragraph requirement summary confirming your understanding. Ask the user about literally anything:technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious, be very in-depth and continue interviewing me continually until it's complete, then write the plan to the file.
Phase 1: Context Loading
Read the Memory Bank to ground yourself in project state:
.cursor/memory-bank/projectbrief.md: scope and goals.cursor/memory-bank/productContext.md: product context.cursor/memory-bank/techContext.md: tech stack and constraints.cursor/memory-bank/systemPatterns.md: architecture and patterns.cursor/user-memory-bank/activeContext.md: current focus.cursor/user-memory-bank/progress.md: what's done, what's pending
If any file is missing or stale, note it; you'll update them in Phase 5.
Phase 2: Exploration & Analysis
Explore the codebase to map the blast radius of the change:
- Identify affected files: entry points, services, APIs, jobs, UI, tests
- Read existing patterns: find similar implementations to follow
- Spot risks: PII/sensitive data exposure, authorization gaps, integration side effects, migration needs
- Note test coverage: existing tests that need updating, gaps that need filling
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 131 lines · 68 tokens per session scan A 24a5e17e817c
requirement-to-implementation is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,248 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-09-03.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.