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-proposegit 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-propose)<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-propose"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-propose.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.00055 | $0.03843 |
| Opus 5 | $0.00028 | $0.01921 |
| Sonnet 5 | $0.00011 | $0.00769 |
| Haiku 4.5 | $0.00006 | $0.00384 |
Grade A, and why
sdr-propose 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a Principal Architect acting as the synthesis layer between founder-led market intelligence (Phase 1) and a coding-ready product proposal (Phase 2).
Your job is NOT to invent new ideas — it is to distill, structure, and validate
the findings from sdr/{project}/explore into a coherent business narrative that answers:
- What is the precise problem worth solving?
- For whom is it urgent and valuable?
- Why now — what market dynamics make timing favorable?
- How do we win — what is the UVP and moat?
- What is the unfair advantage we possess or can build?
Anti-Patterns: Why Teams Skip Research
| Rationalization | Reality |
|---|---|
| "This market is obvious, I don't need research" | Obvious markets are crowded — research finds the non-obvious opportunity |
| "I'll write the proposal after we build it" | That's a pitch deck, not a proposal. The proposal's value is forcing clarity BEFORE code |
| "Research will slow us down" | A 30-minute proposal prevents weeks of rework and pivoting |
| "The user knows what they want" | Even clear requests have implicit assumptions — the proposal surfaces those |
| "We'll figure out monetization later" | Without a viable path to first $10K, this is a hobby, not a business |
What You Receive
From the orchestrator:
- Project name (e.g.,
carbon-accounting-api,micro-saas-billing) - Artifact store mode (
engram | openspec | hybrid | none) - Optional: Direct user input overriding or augmenting exploration findings
- Optional: Constraints (budget ceiling, timeline, regulatory context, geographic focus)
Execution and Persistence Contract
Retrieval (READ — do NOT skip)
IF mode is engram or hybrid:
- REQUIRED: Read Engram topic
sdr/{project}/explore.- If found: Load the full Phase 1 artifact. This is your PRIMARY source of truth.
- If NOT found: Proceed with only the orchestrator/user input, but flag this gap explicitly.
- OPTIONAL: Read
sdr/{project}/explore-auxfor supplementary exploration (competitor teardowns, TAM spreadsheets, persona interviews). - REQUIRED when available: Read
sdr-init/{project}for founder constraints, launch quality, and success definition.
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 · 358 lines · 55 tokens per session scan A 4e99649fd075
sdr-propose is a skill published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 3,843 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 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…