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-donegit 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-done)<a href="https://agentmods.dev/skills/vfarcic/dot-ai/dot-ai-prd-done"><img src="https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-done/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-done"><img src="https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 54 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00027 | $0.04170 |
| Opus 5 | $0.00014 | $0.02085 |
| Sonnet 5 | $0.00005 | $0.00834 |
| Haiku 4.5 | $0.00003 | $0.00417 |
Grade A, and why
dot-ai-prd-done 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete PRD Implementation
Complete the PRD implementation workflow including branch management, pull request creation, and issue closure.
Note: If any gh command fails with "command not found", inform the user that GitHub CLI is required and provide the installation link: https://cli.github.com/
Workflow Steps
0. Implementation Type Detection
FIRST: Determine the type of PRD completion to choose the appropriate workflow
Documentation-Only Completion (Skip PR workflow):
- ✅ Changes are only to PRD files or project management documents
- ✅ No source code changes
- ✅ No configuration changes
- ✅ Feature was already implemented in previous work
- → Use Simplified Workflow (Steps 1, 2-simplified, 5 only)
Code Implementation Completion (Full PR workflow):
- ✅ Contains source code changes
- ✅ Contains configuration changes
- ✅ Contains new functionality or modifications
- ✅ Requires testing and integration
- → Use Full Workflow (Steps 1-6)
1. Pre-Completion Validation
- All PRD checkboxes completed: Verify every requirement is implemented and tested
- Documentation updated: All user-facing docs reflect implemented functionality
- No outstanding blockers: All dependencies resolved and technical debt addressed
- Update PRD status: Mark PRD as "Complete" with completion date
- Archive PRD file: Move completed PRD to
./prds/done/directory to maintain project organization - Update ROADMAP.md (if it exists): Remove the completed feature from
docs/ROADMAP.mdroadmap if the file exists
Note: Tests will run automatically in the CI/CD pipeline when the PR is created. Do not run tests locally during the completion workflow.
2. Branch and Commit Management
For Documentation-Only Completions:
- Commit directly to main:
git add [prd-files]and commit with skip CI flag - Use skip CI commit message: Include CI skip pattern in commit message to avoid unnecessary CI runs
- Common patterns:
[skip ci],[ci skip],***NO_CI***,[skip actions] - Check project's CI configuration for the correct pattern
- Common patterns:
- Push to remote:
git pull --rebase origin main && git push origin mainto sync changes
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 · 343 lines · 27 tokens per session scan A 47a5aaf10be7
dot-ai-prd-done is a skill published in the GitHub repository vfarcic/dot-ai (336 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 4,170 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.