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.
git 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.handoff)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.handoff"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.handoff.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.02295 |
| Opus 5 | $0.00000 | $0.01148 |
| Sonnet 5 | $0.00000 | $0.00459 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
acp.handoff 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 6d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: handoff
🤖 Agent Directive: If you are reading this file, the command
@acp-handoffhas been invoked. Pretend this command was entered with this additional context: "Execute directive `@acp-handoff NOW. 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-03-13 Last Updated: 2026-03-13 Status: Active Scripts: None
Purpose: Generate a context-aware handoff report for transferring work to an agent in a different context (different repository, provider, etc.) Category: Workflow Frequency: As Needed
Arguments
CLI-Style Arguments:
--to <path-or-project>or--target <path-or-project>- Target project path or registered ACP project name
Natural Language Arguments:
@acp.handoff to weaviate-schema- Handoff to a named project@acp.handoff --to ~/projects/other-repo- Handoff to a specific path@acp.handoff- Infer target from conversation context
Argument Mapping: The agent infers intent from context:
- If
--toor--targetprovided → use that as the target project - If target mentioned in natural language → resolve against
~/.acp/projects.yamlor treat as path - If no target specified → infer from conversation context, ask if inference fails
What This Command Does
This command generates a freeform handoff report that captures enough context from the current conversation to enable an agent in a different context (different repository, different provider, etc.) to understand and act on a request. The report explains the problem and the request — not specific implementation steps — so the receiving agent can apply its own judgment within its own codebase.
The handoff is designed for cross-context scenarios where work in one project reveals a need for changes in another. For example, while working in a REST server project, you discover a migration is needed in a Weaviate instance whose schema code lives in a separate repository. Rather than context-switching yourself, you generate a handoff report that another agent session can consume.
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.
- 6d ago First seen · 271 lines · 0 tokens per session scan A 39377e155a3f
acp.handoff 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,295 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.