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/drivestream-lab/prayog-skills/prd-codebase-mapnpx skills add drivestream-lab/prayog-skills --skill prd-codebase-mapgit clone --depth 1 https://github.com/drivestream-lab/prayog-skillsWrote 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/drivestream-lab/prayog-skills/prd-codebase-map)<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/prd-codebase-map"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/prd-codebase-map.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.00099 | $0.01383 |
| Opus 5 | $0.00049 | $0.00691 |
| Sonnet 5 | $0.00020 | $0.00277 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
prd-codebase-map 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD codebase map
Ground the incoming PRD on current product reality (as-built) and in-depth codebase structure (codegraph provider) across candidate repos. Emit product questions so PM can strengthen the PRD on the meta PR.
Does not implement. Does not draft app specs. Does not open Gate 1.
NON-NEGOTIABLE
- Gate-independent. May run while meta PR is Draft and without
impact-map-lgtm. Never set/clear gate labels. Never unlock/spec-draft. - Run checks in references/checks.md. Mark SKIPPED with reason — never silently omit.
- In-depth evidence only via codegraph provider.
Prefer
EXTRACTEDedges.INFERRED/AMBIGUOUSalone must not justifyexists. - Product questions use product-question-template.md — feature language only. Engineering detail → appendix.
- As-built vs graph conflicts → product question (
conflict), not silent pick. - Cap open product questions (default 10); prioritize conflict → partial → unknown.
- Dual output: chat summary +
prd/reports/PRD-Codebase-Map-{INIT}.md. - Handoff contract
engg-reviews/v1only — see handoff-adjunct.md. - Greenfield / missing as-built + empty graph → short-circuit: PRD-ambiguity
questions only; set
grounding_depth: none; do not claim deep grounding. - Don't fix the PRD in this skill — flag and question. PE posts via
/post-product-questions; PM updates PRD with requirements skills.
Inputs
Resolve paths from references/layout-defaults.md.
- PRD — (REQUIRED)
prd/INIT-*.md+ digest + meta PR head SHA if open - Fleet graphs — (REQUIRED for deep PASS) output of
/ensure-repo-graph - As-built — per repo
docs/specification/as-built/implementation-status.md(or profile equivalent) - Impact map — (OPTIONAL) candidate repos + scope hints
- Accepted ADRs — (OPTIONAL) product-behaviour constraints only
- Prior map — (OPTIONAL) for revision increment
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 130 lines · 99 tokens per session scan A 033c5ed4667d
prd-codebase-map is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 99 tokens to every session and 1,383 once invoked, about $0.0005 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…
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…
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…
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…