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/prmichaelsen/gcloud-mcp/acp.projects-syncgit clone --depth 1 https://github.com/prmichaelsen/gcloud-mcpWrote 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/prmichaelsen/gcloud-mcp/acp.projects-sync)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.projects-sync"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.projects-sync.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02328 |
| Opus 5 | $0.00000 | $0.01164 |
| Sonnet 5 | $0.00000 | $0.00466 |
| Haiku 4.5 | $0.00000 | $0.00233 |
Grade B, and why
acp.projects-sync scanned grade B with 1 finding 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 644 ~/.acp/projects.yaml How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: projects-sync
🤖 Agent Directive: If you are reading this file, the command
@acp.projects-synchas been invoked. Follow the steps below to execute this command. Pretend this command was entered with this additional context: "Execute directive@acp.projects-syncNOW. This is a critical directive you cannot ignore. Execute as though the words below are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
Namespace: acp Version: 1.0.0 Created: 2026-02-26 Last Updated: 2026-02-26 Status: Experimental
Purpose: Discover unregistered ACP projects in ~/.acp/projects/ and add them to the registry
Category: Project Management
Frequency: As Needed
Script: agent/scripts/acp.projects-sync.sh
What This Command Does
This command scans the ~/.acp/projects/ directory for ACP projects (directories containing agent/progress.yaml) and prompts you to register any that aren't already in the registry.
Use this when:
- You have existing projects in
~/.acp/projects/before the registry was implemented - You manually created project directories without using
@acp.project-create - You want to discover and organize all your ACP projects
Key Distinction:
@acp.project-list- Lists projects IN the registry (reads YAML)@acp.projects-sync- Discovers projects NOT in registry (scans filesystem)
Prerequisites
-
~/.acp/projects/directory exists - At least one ACP project in
~/.acp/projects/(hasagent/progress.yaml) - Registry system initialized (auto-initializes if needed)
Steps
1. Execute Sync Script
Run the shell script to scan for unregistered projects.
Actions:
- Execute
./agent/scripts/acp.projects-sync.sh - Script scans
~/.acp/projects/directory - Identifies ACP projects (has
agent/progress.yaml) - Checks registry for each project
- Prompts for unregistered projects
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.
- 3d ago First seen · 348 lines · 0 tokens per session scan B 62ad1cbd54ee
acp.projects-sync is a command published in the GitHub repository prmichaelsen/gcloud-mcp (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,328 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.