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-source-of-truthgit 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-source-of-truth)<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-source-of-truth"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-source-of-truth/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/joesagera/spec-driven-research/sdr-source-of-truth"><img src="https://agentmods.dev/badge/skills/joesagera/spec-driven-research/sdr-source-of-truth.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00760 |
| Opus 5 | $0.00018 | $0.00380 |
| Sonnet 5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
sdr-source-of-truth 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDR PRD Handoff
Purpose
You consolidate validated SDR evidence into exactly one development-ready PRD for a solo founder building with AI workflow systems. This is the final SDR deliverable before SDD.
Follow skills/_shared/sdr-phase-common.md, especially Section B1 — Token-Efficient PRD Contract. Intermediate artifacts are internal evidence, not separate final documents.
Inputs
Read the full artifacts for explore, proposal, spec, design, tasks, and verify-report. Never rely on search previews, summaries, or memory.
Before writing the PRD, confirm the verify report decision is GO. If verification is missing or not GO, return blocked and name the phase that must be revisited.
Output
Create the final visible artifact named exactly PRD.
Persist it at the compatibility key sdr/{project}/source-of-truth and, in openspec/hybrid mode, openspec/sdr/{project}/source-of-truth.md. The internal path/key may keep source-of-truth; the user-facing title and handoff name must be PRD.
Start the artifact with:
# PRD
Required sections:
- Founder Context & Constraints
- Product Category and Market Shape
- Target Users, Buyer, and Monetization Assumptions
- MVP Scope and Anti-Scope
- Requirements and Acceptance Criteria Summary
- Technical Architecture and Tech Stack
- Design Direction, Tokens, Components, and Handoff Constraints (when UI exists)
- Implementation-Ready Task Slices
- Risks, Decision Gate, and Open Questions
- SDD Handoff Notes for
sdd-propose
Each section must reference the relevant stable IDs from Section B1 (ASM-*, REQ-*, DEC-*, RSK-*, TASK-*) instead of duplicating long prior-artifact prose. Preserve the final assumptions, requirements, decisions, risks, and task slices with enough detail for a developer or SDD proposal agent to proceed.
For UI/frontend products, the PRD must carry forward the exact design direction, semantic tokens, component/states inventory, accessibility constraints, responsive behavior, known design debt, and implementation guardrails from design.md. Do not reduce the UI contract to "make it modern" — preserve exact values and traceability.
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.
- 11d ago First seen · 74 lines · 37 tokens per session scan A e45f44253f4c
sdr-source-of-truth is a skill published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 760 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…