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 skillmds/skillmd --skill pddgit clone --depth 1 https://github.com/skillmds/skillmdWrote 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/skillmds/skillmd/pdd)<a href="https://agentmods.dev/skills/skillmds/skillmd/pdd"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/pdd/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/skillmds/skillmd/pdd"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/pdd.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.00034 | $0.01367 |
| Opus 5.5 | $0.00014 | $0.00547 |
| Sonnet 5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
pdd 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.
This is a copy
89% identical to pdd — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt-Driven Development
Overview
Transform a rough idea into a detailed design with an implementation plan. The process is iterative: clarify requirements, research, design, plan — moving between phases as needed.
Important Notes
These rules apply across ALL steps:
- User-driven flow: Never proceed to the next step without explicit user confirmation. At each transition, ask the user what they want to do next.
- Iterative: The user can move between requirements clarification and research at any time. Always offer this option at phase transitions.
- Record as you go: Append questions, answers, and findings to project files in real time — don't batch-write at the end.
- Mermaid diagrams: Include diagrams for architectures, data flows, and component relationships in research and design documents.
- Sources: Cite references and links in research documents when based on external materials.
Parameters
- rough_idea (required): The initial concept or idea to develop
- project_dir (optional, default:
specs/{task_name}/): Base directory for all artifacts.{task_name}is derived as kebab-case from the idea (e.g., "build a rate limiter" →rate-limiter). Aligns with Ralph's spec-driven pipeline.
Constraints:
- You MUST ask for all required parameters upfront in a single prompt
- You MUST support multiple input methods: direct text, file path, URL
- You MUST derive
task_namefrom the rough idea as kebab-case - You MUST NOT overwrite an existing project directory — ask for a new path if it already has contents
Steps
1. Create Project Structure
Create the directory and initial files:
{project_dir}/rough-idea.md— the provided rough idea{project_dir}/requirements.md— Q&A record (initially empty){project_dir}/research/— directory for research notes
Inform the user the structure feeds into Ralph's spec-driven presets.
2. Initial Process Planning
Ask the user their preferred starting point:
- Requirements clarification (default)
- Preliminary research on specific topics
- Provide additional context first
What ships with it
1 file 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.
- 4d ago First seen · 148 lines · 34 tokens per session scan A eea31f2464e2
pdd is a skill published in the GitHub repository skillmds/skillmd (1 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 1,367 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to pdd, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
slopless
Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, and cliches.
suiko
A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.
poly-lint-and-format
Running poly lint / poly fmt — --fix, --format pretty|json|toon, --exclude, --config, exit codes, inline suppression, and the check → read-json → fix → re-check loop.
poly-orchestrator
Use poly as the single lint/format gate instead of invoking ruff/oxlint/rustfmt directly — one poly.toml, poly hooks install, poly migrate, CI via the Goldziher/poly setup Action.
poly-mcp
The poly MCP server — the eleven tools and which are read-only vs mutating, the paths/exclude/config/format params, async Tasks for the whole-project phase, and the isError contract.
poly-tiers-and-scope
Five mechanisms decide what actually inspects a file (crates/poly-core/src/registry.rs).