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 commands/signalcompose/claude-tools/startgit clone --depth 1 https://github.com/signalcompose/claude-toolsWhat 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.00008 | $0.00399 |
| Opus 5 | $0.00004 | $0.00199 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
start 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 2d 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
YPM (Your Project Manager) - Multi-project progress tracking system.
This system monitors multiple projects in configured directories and centralizes progress management.
Key Features:
- Automatic information collection from Git history and documentation
- Organize next tasks and priorities
Natural Language (say these to auto-trigger):
- "Update project status" - Scan all projects and update
PROJECT_STATUS.md - "What's the next task?" - Show next actions for active projects
- "Show active projects" - View recently updated projects
- "Create a new project" - Launch the 8-phase project setup wizard
- "Set up git flow" - Configure branch protection and workflow
Skills (use ypm: prefix):
/ypm:project-status-update- Update project status/ypm:next-tasks- Show next tasks/ypm:active-projects- Show active projects/ypm:project-bootstrap- Project setup wizard/ypm:git-workflow-setup- Git workflow setup
Commands (use ypm: prefix):
/ypm:start- Show this welcome message/ypm:help- Show detailed help/ypm:setup- Initial setup/ypm:open- Open project in editor/ypm:export-community- Export to community version/ypm:trufflehog-scan- Security scan
What would you like to do?
YPM is MIT licensed. Provided "AS IS" without warranty. See /ypm:help for details.
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.
- 2d ago First seen · 43 lines · 8 tokens per session scan A fcf090318f17
start is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 8 tokens to every session and 399 once invoked, about $0.0000 per session on Opus 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.
project-recap
Generate a visual project recap for context switching.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).