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 markoblogo/abvx-agent-skills --skill spec-to-prdgit clone --depth 1 https://github.com/markoblogo/abvx-agent-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/markoblogo/abvx-agent-skills/spec-to-prd)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/spec-to-prd"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/spec-to-prd/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/markoblogo/abvx-agent-skills/spec-to-prd"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/spec-to-prd.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.00066 | $0.00341 |
| Opus 5 | $0.00033 | $0.00170 |
| Sonnet 5 | $0.00013 | $0.00068 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
spec-to-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 9d 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
Spec To PRD
Convert current understanding into a durable PRD without re-running the whole discovery session.
Workflow
- Synthesize what is already known from the conversation and repo.
- Use the project's domain language and existing architectural decisions.
- Identify the highest useful seams for implementation and testing.
- Confirm only the few assumptions that would distort the PRD if wrong.
- Produce one PRD artifact:
- issue tracker body;
- markdown file;
- handoff-ready document.
PRD Shape
Include:
- problem statement;
- solution from the user's perspective;
- extensive user stories;
- implementation decisions;
- testing decisions;
- out of scope;
- further notes and open assumptions.
Rules
- Do not dump file paths unless they are durable anchors.
- Do not include code unless a small shape encodes a real decision more precisely than prose.
- Keep scope sharp; explicitly name what is out of scope.
- If discovery is too weak, route back to
rapid-grillingordoc-grounded-grillingfirst.
Final Report
State where the PRD lives, what assumptions remain, and the best next step: issue breakdown, prototype, or execution.
What ships with it
2 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.
- 9d ago First seen · 47 lines · 66 tokens per session scan A cd4671d9664a
spec-to-prd is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 341 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
codex-agent
Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.
css-debug
Use this skill to diagnose CSS and frontend layout issues such as positioning, overflow clipping, Tailwind class conflicts, z-index stacking, and React rendering visibility problems.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.