Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-restore)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.projects-restore"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.projects-restore.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.1 | $0.00000 | $0.01526 |
| Opus 5 | $0.00000 | $0.00763 |
| Sonnet 5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
acp.projects-restore 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 5d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: projects-restore
🤖 Agent Directive: If you are reading this file, the command
@acp.projects-restorehas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 1.0.0 Created: 2026-03-01 Last Updated: 2026-03-01 Status: Experimental
Purpose: Restore/clone missing projects from their registered git origins
Category: Project Management
Frequency: As Needed
Script: agent/scripts/acp.projects-restore.sh
What This Command Does
This command reads ~/.acp/projects.yaml and clones any missing project directories from their stored git_origin URLs. It's designed for restoring projects on a new machine after pushing your ~/.acp configuration.
Use this when:
- You've set up
~/.acpon a new machine and need to clone all your projects - Project directories were deleted and need to be restored
- You want to preview what projects are missing with
--dry-run
Key Distinction:
@acp.projects-sync- Discovers projects on disk and registers them in the registry@acp.projects-restore- Reads the registry and clones projects that are missing from disk
Prerequisites
-
~/.acp/projects.yamlexists with project entries - Projects have
git_originfield set (run@acp.projects-syncto backfill) - Git installed and network access available for cloning
Steps
1. Execute Restore Script
Run the shell script to restore missing projects.
Actions:
- Execute
./agent/scripts/acp.projects-restore.sh [--dry-run] [--install-acp] - Script reads
~/.acp/projects.yamlregistry - Checks each project's directory existence
- Clones missing projects from
git_origin
Expected Outcome: Missing projects cloned to their registered paths
2. Review Results
Check the restore summary.
Actions:
- Review clone count (projects restored)
- Review skip count (already exist, archived, no origin)
- Review errors (failed clones)
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.
- 5d ago First seen · 229 lines · 0 tokens per session scan A 4c146acb6d08
acp.projects-restore 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 1,526 tokens. 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
next
Suggest the most likely next workflow action based on current context.
weekly-summary
Generate weekly work summary from git activity.