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.
git clone --depth 1 https://github.com/unclecode/claude-code-toolsWrote 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/commands/unclecode/claude-code-tools/pp-add)<a href="https://agentmods.dev/commands/unclecode/claude-code-tools/pp-add"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-add/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/commands/unclecode/claude-code-tools/pp-add"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-add.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.00000 | $0.00697 |
| Opus 5.5 | $0.00000 | $0.00279 |
| Sonnet 5.5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
pp-add 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add New Subproject
Create a new subproject in the project structure.
Arguments
$ARGUMENTS
Purpose
Add a new subproject with full file structure. Query should contain:
- Subproject name (folder name)
- Description/purpose
- Optionally: initial scope, dependencies
Execution Instructions
Step 1: Parse Query
Extract from query:
name: Folder name (lowercase, no spaces)title: Human-readable titledescription: What this subproject doesdependencies: Relationships to other subprojects
If query is empty or missing info, ask:
- "Subproject folder name (e.g., 'api', 'frontend'):"
- "Title (e.g., 'REST API Backend'):"
- "Brief description:"
- "Dependencies on other subprojects? (optional)"
Step 2: Create Directory Structure
mkdir -p .context/project/{name}/prds .context/project/{name}/docs .context/project/{name}/archive
Step 3: Copy and Process Templates
Copy subproject templates from ~/.claude/commands/pp-init-assets/templates/subproject/:
# Copy all subproject templates
cp ~/.claude/commands/pp-init-assets/templates/subproject/*.md .context/project/{name}/
Then process placeholders:
{{SUBPROJECT_NAME}}→ name{{SUBPROJECT_TITLE}}→ title{{SUBPROJECT_DESCRIPTION}}→ description{{DATE}}→ current date{{SUBPROJECT_STATUS}}→ "Not Started"- Other placeholders → "TBD" or empty
Step 4: Update Root Files
INDEX.md: Add to subproject table
| {name}/ | Planned | {description} |
STATUS.md: Add to subproject summary table
| {name}/ | - | Not Started |
CODEBASE.md: Add to subproject refs
- `{name}/CODEBASE.md` - {title} files
CHANGELOG.md: Add entry
## {DATE} | Added Subproject: {name}
**Changes**:
- Created {name}/ subproject structure
**Context**:
- {description}
Step 5: Confirm Creation
## Created Subproject: {name}/
**Title**: {title}
**Description**: {description}
**Files created**:
- {name}/INDEX.md
- {name}/STATUS.md
- {name}/TODO.md
- {name}/CHANGELOG.md
- {name}/PRINCIPLES.md
- {name}/CODEBASE.md
- {name}/LESSONS.md
**Updated**:
- Root INDEX.md
- Root STATUS.md
- Root CODEBASE.md
- Root CHANGELOG.md
To start working on this subproject, update STATUS.md to set it as active.
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.
- 1mo ago First seen · 121 lines · 0 tokens per session scan A 253c819102e9
pp-add is a command published in the GitHub repository unclecode/claude-code-tools (4 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 697 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.