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 GongShichen/LuminaCode --skill prd-authoringgit clone --depth 1 https://github.com/GongShichen/LuminaCodeWrote 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/gongshichen/luminacode/prd-authoring)<a href="https://agentmods.dev/skills/gongshichen/luminacode/prd-authoring"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/prd-authoring/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/gongshichen/luminacode/prd-authoring"><img src="https://agentmods.dev/badge/skills/gongshichen/luminacode/prd-authoring.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.00022 | $0.00518 |
| Opus 5.5 | $0.00009 | $0.00207 |
| Sonnet 5.5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
PRD Authoring 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 2mo 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
Write the PRD as a durable project artifact, normally <project_root>/PRD.md.
Inputs:
- User request and any clarified constraints.
- Current working directory and inferred project root.
- Existing product/repository context when present.
- Known time, platform, dependency, data, privacy, and operational constraints.
Required structure:
-
Title and status
- Product/workstream name.
- Authoring date and status: draft, ready for design, revised, or deferred.
-
Problem and goal
- Problem statement in user terms.
- Primary goal and success signal.
- Non-goals that prevent scope creep.
-
Users and scenarios
- Target users or roles.
- Core scenario and at least one failure or edge scenario.
-
Scope
- In scope.
- Out of scope.
- Explicit assumptions.
-
User flows
- Happy path.
- Empty/loading/error path.
- Recovery path when relevant.
-
Functional requirements
- Numbered requirements with observable behavior.
- Required data, persistence, integration, and validation behavior.
- Requirements that must be verified by QA.
-
Interface and data requirements
- Components that must integrate.
- Data fields, ownership, lifecycle, and privacy/security considerations.
- Any known API, event, file, command, or storage boundary.
-
Acceptance criteria
- User-visible acceptance criteria.
- Required artifacts and commands.
- Integration smoke expectations.
-
Risks, dependencies, and open questions
- Risks with owner or mitigation.
- External dependencies.
- Questions that block work, and questions that can proceed with assumptions.
Quality bar:
- The PRD must be concrete enough for UX Design to produce a design without inventing product scope.
- It must be concrete enough for Frontend and Backend to produce separate technical plans.
- It must avoid implementation choices unless the user or repository already constrains them.
- It must preserve the user's architecture; do not simplify multi-component work into one direct-file shortcut.
Handoff:
- Send UX Design an A2A message with the PRD path and a short summary.
- Keep the PRD path in Team dialogue and the Team Acceptance Contract.
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.
- 2mo ago First seen · 74 lines · 22 tokens per session scan A d5eafc463945
PRD Authoring is a skill published in the GitHub repository GongShichen/LuminaCode (9 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…