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 Justinmendezai/The-Adam-Repo --skill to-prdgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/to-prd)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/to-prd"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/to-prd/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/justinmendezai/the-adam-repo/to-prd"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/to-prd.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.00055 | $0.00642 |
| Opus 5 | $0.00028 | $0.00321 |
| Sonnet 5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
to-prd 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 12d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
to-prd
Adapted from Matt Pocock's to-prd. No interview. The conversation already happened — your job is to crystallize it into a doc.
When to use
- Right after a
grill-meorgrill-with-docssession. - After any planning conversation that resolved decisions.
- When the user wants something durable to share or reference.
Not when the conversation hasn't actually settled anything — grill first.
PRD format
# PRD: <short, declarative title>
- Author: <agent + user>
- Date: <YYYY-MM-DD>
- Status: draft | approved | shipped
- Linked ADRs: <list, if any>
## Problem
One paragraph. Whose pain is this? What evidence do we have it's real?
## Goal
One paragraph. What success looks like. Tie to a metric or behavior.
## Non-goals
Bulleted. The things this PRD explicitly is NOT solving.
## Proposed solution
One to three paragraphs. The shape of the change. Not the implementation — the user-facing shape and the system-level architecture in broad strokes.
## Success criteria
Bulleted, each measurable:
- SC-1: <description> — <how we'll measure>
- SC-2: ...
## Risks and mitigations
- Risk 1 — Mitigation
- Risk 2 — Mitigation
## Open questions
Anything still unresolved. Flag clearly. The reader should know what's settled vs. deferred.
## Modules touched
List of files or modules this PRD will affect. (This is the module-design check from Matt's original — caring about modules at PRD time.)
Workflow
- Skim the conversation. Identify decisions, not narrative.
- Map decisions to PRD sections.
- Quote the user's words for goals and non-goals where you have them — don't paraphrase to soften.
- List modules the change will touch. If you can't, dispatch an
exploresubagent to find them. - Show the draft. Let the user redline.
Anti-patterns
- Inventing content the conversation didn't resolve. If a section is empty, leave it empty and flag it under Open questions.
- Re-interviewing. The whole point is to skip that.
- Module list as "everything." Be specific. If the change touches 30 files, the slice is too big — go back to grilling.
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.
- 12d ago First seen · 73 lines · 55 tokens per session scan A 94fba7ff4e54
to-prd is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 55 tokens to every session and 642 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…