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-tasksgit 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-tasks)<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-tasks"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-tasks.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.00038 | $0.01344 |
| Opus 5 | $0.00019 | $0.00672 |
| Sonnet 5 | $0.00008 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
sdr-tasks 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 7d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDR Tasks — Coding Task Breakdown
Purpose
You are responsible for IMPLEMENTATION TASK BREAKDOWN. You take the founder intake, proposal, spec, and design, then produce vertical coding slices that feed the final visible PRD (internal source-of-truth) and later sdd-propose.
GTM, finance, pricing, SEO/content calendars, CRM flows, and launch operations are excluded from this phase unless they directly create product behavior that must be implemented.
What You Receive
- Project name
- Artifact store mode (
engram | openspec | hybrid | none) - Prior artifacts:
sdr-init/{project},sdr/{project}/proposal,sdr/{project}/spec,sdr/{project}/design
Execution and Persistence Contract
Follow skills/_shared/sdr-phase-common.md.
- engram: read required prior artifacts and save as
sdr/{project}/tasks. - openspec: write
openspec/sdr/{project}/tasks.md. - hybrid: do both, Engram primary.
- none: return inline only.
What to Do
Step 1: Analyze Inputs
Extract:
- MUST/SHOULD requirements and acceptance criteria
- architecture and tech-stack constraints
- design decisions, UI components, design tokens, and DESIGN.md handoff constraints when UI exists
- founder constraints: solo capacity, budget, timeline, risk tolerance, launch quality
- dependencies, external integrations, and risk mitigations
Apply Section B1 of skills/_shared/sdr-phase-common.md: carry forward relevant ASM-*, REQ-*, DEC-*, and RSK-* IDs; create stable TASK-* IDs for implementation slices.
Step 2: Create Vertical Coding Slices
Every task must deliver a working, testable product increment end-to-end and map back to design decisions/components where applicable.
Bad: “Build all backend APIs.”
Good: “User can create an account: schema + API + UI + validation + tests.”
For UI products, include explicit slices for component states, accessibility behavior, responsive behavior, and design debt cleanup identified in design.md.
Step 3: Produce tasks.md
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.
- 7d ago First seen · 138 lines · 38 tokens per session scan A 3a9602f3579a
sdr-tasks is a skill published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 1,344 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…