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-updategit 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-update)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.project-update"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.project-update.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.01979 |
| Opus 5 | $0.00000 | $0.00989 |
| Sonnet 5 | $0.00000 | $0.00396 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
acp.project-update 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: project-update
🤖 Agent Directive: If you are reading this file, the command
@acp.project-updatehas 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: Update project metadata in the global registry Category: Project Management Frequency: As Needed
What This Command Does
This command updates metadata for a project in ~/.acp/projects.yaml, allowing you to modify status, description, type, tags, and related projects. It provides granular control over project metadata without requiring manual YAML editing.
Use this command to keep project metadata current as projects evolve, mark projects as archived when completed, add tags for organization, link related projects, or correct project information. All updates automatically update the last_modified timestamp.
Unlike @acp.project-info which displays information, this command modifies the registry. It supports multiple update operations in a single invocation.
Prerequisites
- Global ACP infrastructure initialized (
~/.acp/exists) - Project registry exists (
~/.acp/projects.yaml) - Project is registered in the registry
Steps
1. Parse Arguments
Extract project name and update options.
Actions:
- Parse project name (required)
- Parse update flags (--status, --description, --type, --git-origin, --git-branch, etc.)
- Validate at least one update option provided
Expected Outcome: Arguments parsed successfully
2. Validate Project Exists
Check that the project is in the registry.
Actions:
- Load registry with
yaml_parse() - Check project exists with
yaml_has_key() - Show error if not found
Expected Outcome: Project found in registry
3. Validate Update Values
Check that provided values are valid.
Actions:
- Validate status is one of: active, archived, paused
- Validate other fields as needed
- Show errors for invalid values
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 · 308 lines · 0 tokens per session scan A e7c2e6d7e220
acp.project-update 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,979 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.