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/jh941213/codex-lattice/prdnpx skills add jh941213/codex-lattice --skill prdgit clone --depth 1 https://github.com/jh941213/codex-latticeWrote 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/jh941213/codex-lattice/prd)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/prd"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/prd.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 | $0.00095 | $0.00512 |
| Opus 5 | $0.00048 | $0.00256 |
| Sonnet 5 | $0.00019 | $0.00102 |
| Haiku 4.5 | $0.00010 | $0.00051 |
Grade A, and why
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 4d 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.
What it actually says
PRD
Codex에서는 $prd 스킬로 기획 산출물을 만든다.
산출물
prd/
├── CPS.md
├── PRD.md
├── MARKET.md
├── USERS.md
├── FEATURES.md
├── RISKS.md
├── SPEC.md
└── APPENDIX.md
절차
- 기존
prd/가 있으면 이어서 진행할지 확인한다. - 복잡도 판정:
- Low: 단순 기능/도구/CLI, 리서치 최소화.
- Mid: 새 모듈/서비스/라이브러리, 핵심 리서치만 수행.
- High: 새 제품/SaaS/플랫폼, 리서치와 인터뷰를 충분히 수행.
- CPS를 먼저 확정한다:
- Context: 어떤 상황/환경인가.
- Problem: 어떤 문제가 있고 정량 지표는 무엇인가.
- Solution: 성공 후 어떤 상태가 되어야 하는가.
- 필요한 질문은 한 번에 1-3개만 한다.
- 기능은 사용자 스토리, 인수조건, 우선순위, 제외 범위까지 쓴다.
- SPEC에는 기술 스택, 아키텍처, API, 데이터 모델, 보안/배포 제약을 기록한다.
- 마지막에
FEATURES.md와SPEC.md가 서로 맞는지 검증한다.
리서치
시장/기술 정보가 최신성에 민감하면 공식 문서, GitHub, 웹 검색 결과를 확인하고 출처를 APPENDIX.md에 남긴다.
출력
## PRD Result
- created/updated:
- unresolved questions:
- assumptions:
- next skill:
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.
- 4d ago First seen · 57 lines · 95 tokens per session scan A b18f19008e3f
prd is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 512 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…