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 agentmods add skills/joesagera/spec-driven-research/sdr-initnpx skills add JoeSagera/Spec-Driven-Research --skill sdr-initgit 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-init)<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-init"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-init.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.00036 | $0.00685 |
| Opus 5 | $0.00018 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
sdr-init 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDR Init — Founder Intake
Purpose
You establish the research charter for a solo founder who says: “I have this amazing idea; I wonder if it is realistic.” SDR starts with founder context, not generic desk research.
What You Receive
- Project name
- Founder idea in plain language
- Artifact store mode (
engram | openspec | hybrid | none) - Execution mode (
automatic | interactive)
What to Do
- Capture the raw idea and initial product category.
- Infer the likely market shape: B2B/B2C, regulated/unregulated, marketplace/SaaS/content/tooling, greenfield/brownfield.
- Apply
skills/_shared/sdr-phase-common.mdSection B1 before asking anything:- classify each prompt as
founder-only,AI-safe,mixed, orvalidation-checkpoint - ask only
founder-onlyandvalidation-checkpointquestions by default - split
mixedquestions and ask only the missing founder-owned part - turn
AI-safeitems into recommendations with tradeoff and founder override point
- classify each prompt as
- Build a founder interview brief covering:
- founder constraints: budget, time, team, domain expertise, risk tolerance
- target users and buyer/user split
- monetization assumptions
- desired launch quality and success definition
- technical preferences, existing assets, and AI workflow expectations
- Assign stable
ASM-*IDs to founder facts, assumptions, constraints, and validation checkpoints. IDs are append-only; preserve existing IDs when updating. - In automatic mode, proceed with explicit
ASM-*assumptions unless a critical founder-only unknown makes research impossible. In interactive mode, batch the highest-leverage founder-owned questions first. - Persist the init artifact with the compressed evidence envelope from Section B1.
Persistence
Follow skills/_shared/sdr-phase-common.md.
- Engram topic:
sdr-init/{project} - Openspec/hybrid path:
openspec/sdr/{project}/init.md
Result Envelope
Return the shared envelope from skills/_shared/sdr-phase-common.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.
- 5d ago First seen · 71 lines · 36 tokens per session scan A 18a44d30eb14
sdr-init is a skill published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 685 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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…