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.project-removegit 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.project-remove)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.project-remove"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.project-remove.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.02389 |
| Opus 5 | $0.00000 | $0.01195 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade C, and why
acp.project-remove scanned grade C 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Manually delete directory: `rm -rf /path/to/project` How it starts
The opening of the file, as written. The whole thing — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: project-remove
🤖 Agent Directive: If you are reading this file, the command
@acp.project-removehas been invoked. Follow the steps below to execute this command. Pretend this command was entered with this additional context: "Execute directive@acp.project-removeNOW. 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: Remove a project from the global registry with optional directory deletion Category: Project Management Frequency: As Needed
What This Command Does
This command removes a project from the global ACP project registry at ~/.acp/projects.yaml. It provides two removal modes:
- Registry Only (default): Removes project metadata from registry, preserves directory
- Complete Removal (--delete-files): Removes from registry AND deletes project directory
The command includes safety features:
- Confirmation prompts before removal
- Extra confirmation for directory deletion (requires typing "DELETE")
- Warning if removing the current project
- Updates
current_projectto empty if removing current - Lists remaining projects after removal
Use this when: Cleaning up old projects, removing archived projects, or completely deleting abandoned projects.
Prerequisites
- Global ACP installed (
~/.acp/exists) - Project registry exists (
~/.acp/projects.yaml) - Target project registered in registry
Steps
1. Run Shell Script
Execute the project-remove script with the project name and options.
Actions:
- Run:
./agent/scripts/acp.project-remove.sh <project-name> [options] - Script validates project exists in registry
- Script displays project information
- Script prompts for confirmation
- Script removes from registry
- Script optionally deletes directory
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.
- 4d ago First seen · 380 lines · 0 tokens per session scan C 82fd2e05268f
acp.project-remove 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,389 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.