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.design-creategit 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.design-create)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.design-create"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.design-create.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.02048 |
| Opus 5 | $0.00000 | $0.01024 |
| Sonnet 5 | $0.00000 | $0.00410 |
| Haiku 4.5 | $0.00000 | $0.00205 |
Grade A, and why
acp.design-create 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: design-create
🤖 Agent Directive: If you are reading this file, the command
@acp.design-createhas been invoked.This is a CREATION command - you will create files directly, no shell scripts needed.
Follow the steps below to create a design document with proper namespace and automatic package updates.
Namespace: acp Version: 1.0.0 Created: 2026-02-21 Last Updated: 2026-02-21 Status: Active Scripts: None
Purpose: Create design documents with namespace enforcement, draft support, and automatic package updates Category: Creation Frequency: As Needed
What This Command Does
This command creates a new design document with intelligent namespace handling, optional draft file support, and automatic updates to package.yaml and README.md. It provides a guided workflow for creating well-structured design documents that follow ACP conventions.
Key Features:
- Context-aware (detects if in package vs project)
- Automatic namespace enforcement
- Draft file support with clarification workflow
- Auto-updates package.yaml and README.md
- Uses design.template.md as base
Use this when: Creating a new design document in an ACP project or package.
Prerequisites
- ACP installed in current directory
- Design template exists (agent/design/design.template.md)
- (Optional) Draft file prepared if using draft workflow
Arguments
Context Capture Arguments (optional — passed to @acp.clarification-capture directive):
| Argument | Alias | Behavior |
|---|---|---|
--from-clarification <file> |
--from-clar |
Capture decisions from a specific clarification file |
--from-clarifications |
--from-clars |
Capture from all recent clarifications |
--from-chat-context |
--from-chat |
Capture decisions from chat conversation |
--from-context |
(none) | Shorthand for all sources (clarifications + chat) |
--include-clarifications |
(none) | Alias for --from-clars |
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 · 287 lines · 0 tokens per session scan A 083232ceddb9
acp.design-create 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,048 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.
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.