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.project-info)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.project-info"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.project-info.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.01999 |
| Opus 5 | $0.00000 | $0.01000 |
| Sonnet 5 | $0.00000 | $0.00400 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
acp.project-info 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 7d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: project-info
🤖 Agent Directive: If you are reading this file, the command
@acp.project-infohas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 1.0.0 Created: 2026-02-25 Last Updated: 2026-02-25 Status: Experimental
Purpose: Display detailed information about a specific project from the global registry Category: Project Management Frequency: As Needed
What This Command Does
This command displays comprehensive information about a project registered in ~/.acp/projects.yaml, including metadata, timestamps, tags, related projects, dependencies, and directory status. It provides a complete view of a project's configuration and current state.
Use this command to understand project details, check project status, view relationships with other projects, and verify project directory existence. It's particularly useful when working with multiple projects in the global workspace to quickly understand project context.
Unlike @acp.project-list which shows all projects in a summary view, @acp.project-info focuses on a single project and displays all available metadata in detail.
Prerequisites
- Global ACP infrastructure initialized (
~/.acp/exists) - Project registry exists (
~/.acp/projects.yaml) - Project is registered in the registry
Steps
1. Validate Arguments
Check that project name is provided.
Actions:
- Verify project name argument is present
- Show usage if missing
Expected Outcome: Project name identified
2. Load Registry
Read the project registry file.
Actions:
- Get registry path via
get_projects_registry_path() - Check if registry file exists
- Parse registry with
yaml_parse()
Expected Outcome: Registry loaded successfully
3. Validate Project Exists
Check that the project is in the registry.
Actions:
- Use
yaml_has_key()to check for project - If not found, list available projects
- Show helpful error message
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.
- 7d ago First seen · 313 lines · 0 tokens per session scan A 356b04f12c03
acp.project-info 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,999 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.