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 vfarcic/dot-ai --skill dot-ai-prd-update-decisionsgit clone --depth 1 https://github.com/vfarcic/dot-aiWrote 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/vfarcic/dot-ai/dot-ai-prd-update-decisions)<a href="https://agentmods.dev/skills/vfarcic/dot-ai/dot-ai-prd-update-decisions"><img src="https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-update-decisions/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/vfarcic/dot-ai/dot-ai-prd-update-decisions"><img src="https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-update-decisions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.01062 |
| Opus 5 | $0.00010 | $0.00531 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
dot-ai-prd-update-decisions 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 10d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Update Decisions Slash Command
Instructions
You are updating a PRD based on design decisions, strategic changes, and architectural choices made during conversations. This command captures conceptual changes that may not yet be reflected in code but affect requirements, approach, or scope.
Process Overview
- Identify Target PRD - Determine which PRD to update
- Analyze Conversation Context - Review discussions for design decisions and strategic changes
- Identify Decision Points - Find architecture, workflow, requirement, or scope changes
- Map to PRD Sections - Determine which parts of the PRD need updates
- Propose Updates - Suggest changes to requirements, approaches, and constraints
- Update Decision Log - Record new decisions with rationale and impact
Step 1: PRD Analysis
Ask the user which PRD to update, then:
- Read the PRD file from
prds/[issue-id]-[feature-name].md - Understand current requirements, approach, and constraints
- Identify areas most likely to be affected by design decisions
Step 2: Conversation Analysis
Review the conversation context for decision-making patterns:
Design Decision Indicators
Look for conversation elements that suggest strategic changes:
- Workflow changes: "Let's simplify this to..." "What if we instead..."
- Architecture decisions: "I think we should use..." "The better approach would be..."
- Requirement modifications: "Actually, we don't need..." "We should also include..."
- Scope adjustments: "Let's defer this..." "This is more complex than we thought..."
- User experience pivots: "Users would prefer..." "This workflow makes more sense..."
Specific Decision Types
- Technical Architecture: Framework choices, design patterns, data structures
- User Experience: Workflow changes, interface decisions, interaction models
- Requirements: New requirements, modified requirements, removed requirements
- Scope Management: Features added, deferred, or eliminated
- Implementation Strategy: Phasing changes, priority adjustments, approach modifications
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.
- 10d ago First seen · 107 lines · 21 tokens per session scan A 1f3d4a589a74
dot-ai-prd-update-decisions is a skill published in the GitHub repository vfarcic/dot-ai (336 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,062 once invoked, about $0.0001 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.
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…