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/opengit 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.00007 | $0.01705 |
| Opus 5 | $0.00003 | $0.00852 |
| Sonnet 5 | $0.00001 | $0.00341 |
| Haiku 4.5 | $0.00001 | $0.00170 |
Grade A, and why
open 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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YPM - Open Project in Editor
Open a YPM-managed project in specified editor.
Prerequisites:
- Run
/ypm:setupfirst if~/.ypm/config.ymldoesn't exist - Run
/ypm:updatefirst if~/.ypm/PROJECT_STATUS.mddoesn't exist
Subcommands
- (no args): Select from list (excluding ignored, open with default editor)
<project> [editor]: Open project with specified editorall: Select from all projects including ignoredignore-list: Show ignored projects listadd-ignore: Add project to ignore listremove-ignore: Remove from ignore list--editor [name]: View/set default editor
Usage Examples
/ypm:open # Normal mode (default editor)
/ypm:open myproject # Open myproject with default editor
/ypm:open myproject cursor # Open myproject with Cursor
/ypm:open myproject terminal # Open myproject in Terminal.app
/ypm:open all # Show all mode
/ypm:open --editor # Show current default editor
/ypm:open --editor cursor # Set default to Cursor
/ypm:open ignore-list # Show ignore list
/ypm:open add-ignore # Add to ignore
/ypm:open remove-ignore # Remove from ignore
Supported Editors: code (VS Code), cursor (Cursor), zed (Zed), terminal (Terminal.app)
Execution Steps
Common STEP: Check Arguments
Check arguments and branch to corresponding mode:
- No args -> Mode 1: Normal mode
<project> [editor]-> Mode 1: Normal mode (direct project specification)all-> Mode 2: Show all modeignore-list-> Mode 3: Ignore listadd-ignore-> Mode 4: Add ignoreremove-ignore-> Mode 5: Remove ignore--editor [name]-> Mode 6: Editor settings
Mode 1: Normal Mode (no args or project name specified)
STEP 1: Check config.yml and Editor CLI
1-1. Get default editor from ~/.ypm/config.yml
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 · 243 lines · 7 tokens per session scan A 5e3bed5f8ce4
open is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 7 tokens to every session and 1,705 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.