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.
/plugin marketplace add signalcompose/claude-toolsnpx agentmods add plugins/signalcompose/claude-tools/ypmgit clone --depth 1 https://github.com/signalcompose/claude-toolsGrade A, and why
ypm 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
{
"name": "ypm",
"description": "Multi-project progress tracking system powered by Claude Code. Automatically tracks status of multiple projects from Git history and documentation.",
"author": {
"name": "Hiroshi Yamato",
"email": "[email protected]",
"url": "https://hiroshiyamato.com"
},
"homepage": "https://github.com/signalcompose/ypm",
"repository": "https://github.com/signalcompose/ypm",
"license": "MIT",
"keywords": [
"project-management",
"multi-project",
"progress-tracking",
"git",
"workflow",
"productivity"
]
}
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 · 21 lines scan A ce67f7c2a8e3
ypm is a plugin published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
atlassian-mcp-server
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
scrumboy-board-operator
Agent plugin with Skills for operating Scrumboy boards through its MCP and Agoragentic APIs.
enablement-crm-pack
CRM workflow bundle with reusable context, account planning, deal inspection, forecasting, and renewals.
beans-prime
Configure Claude Code to track work using Beans.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…