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 agentmods add skills/promptdriven/pdd/checkup-simplifynpx skills add promptdriven/pdd --skill checkup-simplifygit clone --depth 1 https://github.com/promptdriven/pddWhat 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 | $0.00000 | $0.00471 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
checkup-simplify 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 3d 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
Checkup simplify (multi-provider workflow)
Use this skill when the user asks for conservative cleanup of already changed source files,
similar to Claude Code /simplify, but the active agent may be Cursor, Codex, Gemini, or OpenCode.
When to use
- User mentions
pdd checkup simplify,/simplify, or wants a verified, conservative cleanup of a bounded file set from a git diff. - User wants parity with PDD's simplify selection rules without running the full CLI.
When not to use
- Greenfield feature work or large refactors across the repo.
- Replacing
pdd checkupPR review loops or contract/coverage gates.
Workflow
- Establish scope — Only files the user (or PDD) listed. Ask if the allowlist is unclear.
- Read the diff — Understand what already changed; simplify that, do not redesign.
- Three passes — Quality (dead code, clarity), efficiency (control flow), consistency (style).
- Edit minimally — Prefer the candidate touching the fewest files that still improves the code.
- Preserve behavior — Do not change semantics without tests; skip uncertain edits.
- Summarize — List files touched and what you intentionally skipped.
PDD parity rules (if emulating pdd checkup simplify)
- Reject / refuse out-of-scope file edits.
- With multiple attempts, only claim success when configured verification would pass.
- For
--stagedworkflows, never overwrite unstaged content on the same paths. - Load
[tool.pdd.checkup.simplify]from the repository root, not the current subdirectory.
Provider notes
- Claude Code — Production path uses
/simplifyviapdd checkup simplify --apply. - Codex / Gemini / OpenCode — Use the matching
pdd/prompts/checkup_simplify_invoke_*_LLM.promptasset as the invocation template until PDD wires them in code.
Reference prompts in repo
pdd/prompts/checkup_simplify_workflow_LLM.promptdocs/checkup_simplify_providers.md
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A fd349a61396c
checkup-simplify is a skill published in the GitHub repository promptdriven/pdd (861 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 tokens. 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
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
发展目标 vs 发展过程
当需要避免'目标-手段混淆'时，区分理想状态（目标）和实现路径（过程），避免用发达国家的现状作为评判发展中国家的标准。适用于政策分析、改革设计、组织转型、个人成长规划。.
code-runner
安全代码执行（Python/JavaScript/Bash脚本运行、超时控制、输出捕获）.
code-review
Code review for issues, style consistency, best practices—use for full code evaluation; not for debugging specific errors or fixing individual style violations.
ps2-recomp-Agent-SKILL
Expert PS2 game reverse engineering and PS2Recomp pipeline porting. Use for ISO/ELF extraction, MIPS R5900 analysis, TOML configuration, syscall stubbing, C++ runtime debugging, and GhydraMCP interaction. Use when the user mentions PS2Recomp, ps2xRuntime, cmake incremental build, SLES, SLUS, out.cpp, runner/.cpp, MIPS…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.