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/signalcompose/claude-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/signalcompose/claude-tools/help)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/help"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/help/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/signalcompose/claude-tools/help"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/help.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.00011 | $0.00868 |
| Opus 5.5 | $0.00004 | $0.00347 |
| Sonnet 5.5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
help 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YPM (Your Project Manager) - Help
Overview
YPM monitors multiple projects in configured directories and centralizes progress management.
Available Skills (Auto-triggered)
Skills are automatically activated when you ask related questions in natural language.
| Skill | Trigger Examples |
|---|---|
/ypm:project-status-update |
"update project status", "scan projects", "プロジェクトのステータス更新" |
/ypm:next-tasks |
"what should I work on next", "next tasks", "次何やる" |
/ypm:active-projects |
"show active projects", "what am I working on", "アクティブなプロジェクト" |
/ypm:project-bootstrap |
"create a new project", "bootstrap project", "新しいプロジェクト作成" |
/ypm:git-workflow-setup |
"set up git flow", "protect branches", "Gitフロー設定" |
Available Commands (Manual invocation)
Project Management
/ypm:start
Show welcome message and quick commands.
/ypm:setup
Initialize YPM data directory and configuration.
/ypm:open
Open project in preferred editor.
- Basic: Select from project list
<project>: Open with default editor<project> <editor>: Open with specific editor--editor: View/set default editorall: Show all including ignoredadd-ignore/remove-ignore: Manage ignore list
Legacy Commands (Redirected to Skills)
These commands still work but redirect to their skill equivalents:
| Legacy Command | Redirects To |
|---|---|
/ypm:update |
/ypm:project-status-update |
/ypm:next |
/ypm:next-tasks |
/ypm:active |
/ypm:active-projects |
/ypm:new |
/ypm:project-bootstrap |
/ypm:setup-gitflow |
/ypm:git-workflow-setup |
Security & Export
/ypm:export-community
Export private repository to public community version.
- Interactive setup on first run
- Automatic export on subsequent runs
- TruffleHog security scan integration
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 · 133 lines · 11 tokens per session scan A 9826f3abe62a
help is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 868 once invoked, about $0.0000 per session on Opus 5.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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
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.