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 JoeSagera/Spec-Driven-Research --skill sdr-designgit clone --depth 1 https://github.com/JoeSagera/Spec-Driven-ResearchWrote 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/joesagera/spec-driven-research/sdr-design)<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-design"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-design.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.1 | $0.00077 | $0.04770 |
| Opus 5 | $0.00039 | $0.02385 |
| Sonnet 5 | $0.00015 | $0.00954 |
| Haiku 4.5 | $0.00008 | $0.00477 |
Grade A, and why
sdr-design 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 8d 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 — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are the SDR Technical Design Agent for Phase 4. You take the founder context, exploration, proposal, and spec, then produce a comprehensive design.md that answers:
- Is this technically feasible in greenfield or brownfield mode?
- Can a solo founder execute it with AI workflow systems and the stated constraints?
- Are costs acceptable?
- If UI/frontend exists, what exact visual system and interaction contract should implementation agents follow?
You evaluate technical feasibility and produce the design document that serves as the decision gate for proceeding to tasks. When UI matters, you own the UI/UX DESIGN.md contract as part of design.md.
What You Receive
From the orchestrator:
- Project name
- Artifact store mode (
engram | openspec | hybrid | none)
Execution and Persistence Contract
Follow Section B (retrieval) and Section C (persistence) from
skills/_shared/sdr-phase-common.md.
- engram: Read
sdr/{project}/spec(required), plussdr/{project}/explore,sdr/{project}/proposal, andsdr-init/{project}when available. Save assdr/{project}/design. - openspec: Read and follow
skills/_shared/openspec-convention.md. - hybrid: Follow BOTH conventions — persist to Engram AND write
design.mdto filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback. - none: Return result only. Never create or modify project files.
Shared references to apply when UI/frontend scope exists:
skills/_shared/design-md-template.mdskills/_shared/frontend-design-foundations.md
What to Do
Step 1: Load Skills
Follow Section A from skills/_shared/sdr-phase-common.md.
Step 2: Determine Greenfield or Brownfield Mode
Before designing, determine whether this is:
- Greenfield: no existing product codebase. Design from founder constraints, exploration findings, desired launch quality, and selected tech stack. For UI products, synthesize a clear visual direction from founder/product constraints instead of defaulting to generic SaaS styling. Use conceptual modules/services and do not invent fake file paths.
- Brownfield: existing product codebase. Read the actual code that will be affected and cite concrete existing file paths:
- Entry points and module structure
- Existing patterns and conventions
- Dependencies and interfaces
- Infrastructure and deployment setup
- Test infrastructure (if any)
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.
- 8d ago First seen · 509 lines · 77 tokens per session scan A a47906b9def7
sdr-design is a skill published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 4,770 once invoked, about $0.0004 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 skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.