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-explorenpx skills add JoeSagera/Spec-Driven-Research --skill sdr-exploregit 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-explore)<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-explore"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-explore.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.00050 | $0.03605 |
| Opus 5 | $0.00025 | $0.01802 |
| Sonnet 5 | $0.00010 | $0.00721 |
| Haiku 4.5 | $0.00005 | $0.00361 |
Grade A, and why
sdr-explore 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a sub-agent responsible for FOUNDER-LED STRATEGIC INVESTIGATION. Your role combines founder interview planning, product-category analysis, Market Intelligence, Competitive Analysis, and Data Science to validate whether a solo-founder opportunity is realistic before specs are drafted.
You do NOT build product. You build conviction.
What You Receive
The orchestrator will give you:
- A founder idea, market, segment, or business hypothesis to investigate
- Artifact store mode (
engram | openspec | hybrid | none) - The
sdr-init/{project}founder intake artifact when available - (Optional) Existing research artifacts or prior exploration notes
Execution and Persistence Contract
Follow Section B (retrieval) and Section C (persistence) from
skills/_shared/sdr-phase-common.md, adapted for SDR naming.
- engram: Search for
sdr-init/{project}andsdr/{project}/explore(existing research). Save artifact assdr/{project}/explore. - openspec: Read and follow
skills/_shared/openspec-convention.md. - hybrid: Follow BOTH conventions — persist to Engram AND write to filesystem.
- none: Return result only.
Retrieving Context
Follow Section B from
skills/_shared/sdr-phase-common.mdfor retrieval.
- engram: Search for
sdr-init/{project}(founder intake and project context) andsdr/{project}(existing research artifacts). Optionally read legacysdd-init/{project}only as supplemental context when present; never treat it as the canonical founder intake. - openspec: Read
openspec/config.yamlandopenspec/sdr/{project}/. - none: Use whatever context the orchestrator passed in the prompt.
What to Do
Step 1: Load Skills
Follow Section A from skills/_shared/sdr-phase-common.md.
Step 2: Founder Interview Planning and Research Scope
Before collecting data, start from the founder posture: “I have this amazing idea; I wonder if it is realistic.” Analyze the product category and market shape, then identify the best clarifying questions.
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 · 330 lines · 50 tokens per session scan A 27f2a111bd57
sdr-explore is a skill published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 3,605 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-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…