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-status)<a href="https://agentmods.dev/commands/unclecode/claude-code-tools/pp-status"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-status/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-status"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-status.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.00541 |
| Opus 5.5 | $0.00000 | $0.00216 |
| Sonnet 5.5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
pp-status 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Summary
Show compact status of the entire project.
Arguments
$ARGUMENTS
Purpose
Quick overview of project state without loading full context. Shows:
- Active subproject and its focus
- All subprojects status
- In-progress tasks
- Recent changes
- Any blockers
Execution Instructions
Step 1: Read Status Files
Read these files:
.context/project/INDEX.md(get active subproject + project summary).context/project/{active}/STATUS.md.context/project/{active}/TODO.md.context/project/{active}/CHANGELOG.md(last 2-3 entries)
Step 2: Parse Optional Query
If query provided, focus on:
- Specific subproject:
/pp-status maya - Specific aspect:
/pp-status tasksor/pp-status blockers
Step 3: Generate Compact Summary
Output format:
## Project Status: {PROJECT_NAME}
### Active: {subproject}/
**Phase**: {current phase}
**Focus**: {one-line current focus}
### In Progress
{tasks marked [>], one line each with T### ID}
### Pending (Next Up)
{next 3-5 pending tasks}
### Subprojects
| Name | Status | Phase |
|------|--------|-------|
{table from root STATUS.md}
### Blockers
{any blocked items from STATUS.md, or "None"}
### Recent Activity
{last 2-3 changelog entries, date + one-line summary}
---
Last updated: {date from STATUS.md}
Step 4: Subproject-Specific Status
If query specifies a subproject:
## Subproject Status: {name}/
**Phase**: {phase}
**Status**: {status}
### What's Working
{bullet list}
### What's Blocked
{bullet list or "Nothing blocked"}
### Current Focus
{numbered list}
### Tasks
**In Progress**: {count}
**Pending**: {count}
**Completed**: {count}
### Next Actions
{from STATUS.md}
Query Examples
# Full project status
/pp-status
# Specific subproject
/pp-status maya
# Focus on tasks only
/pp-status tasks
# Focus on blockers
/pp-status blockers
Output Notes
- Keep it COMPACT - fits in one screen
- Use tables for multiple items
- One line per item max
- Show counts, not full lists
- Highlight blockers prominently
- This is READ-ONLY (no modifications)
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 · 118 lines · 0 tokens per session scan A 3d03d0cb1550
pp-status 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 541 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.