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.clarification-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.clarification-create)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.clarification-create"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.clarification-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.03427 |
| Opus 5 | $0.00000 | $0.01714 |
| Sonnet 5 | $0.00000 | $0.00685 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
acp.clarification-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 4d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: clarification-create
🤖 Agent Directive: If you are reading this file, the command
@acp-clarification-createhas been invoked. Follow the steps below to execute this command. Pretend this command was entered with this additional context: "Execute directive `@acp-clarification-create 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-02-25 Last Updated: 2026-02-25 Status: Active
Purpose: Create clarification documents from file input or chat to gather detailed requirements Category: Creation Frequency: As Needed
Arguments
CLI-Style Arguments:
--file <path>or-f <path>- Path to source file to analyze for clarifications--title <title>or-t <title>- Title for the clarification document--autoor-a- Automatically generate questions without user review
Natural Language Arguments:
@acp.clarification-create from draft file- Analyze draft and create clarifications@acp.clarification-create for feature X- Create clarifications about feature X@acp.clarification-create- Interactive mode (no file)
Argument Mapping: The agent infers intent from context:
- If file path mentioned → Read and analyze that file
- If topic mentioned → Create clarifications about that topic
- If no arguments → Interactive chat-based clarification creation
What This Command Does
This command creates structured clarification documents following the agent/clarifications/clarification-{N}-{title}.template.md format. It can analyze existing files (drafts, designs, requirements) to identify gaps and generate targeted questions, or work interactively via chat to gather requirements.
Clarification documents use a hierarchical structure (Items > Questions > Bullet points) to organize related questions logically. They include response markers (>) for users to provide answers inline, making it easy to capture detailed requirements without lengthy back-and-forth conversations.
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.
- 4d ago First seen · 438 lines · 0 tokens per session scan A 8c5d428b693e
acp.clarification-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 3,427 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
organize-files
Organize and rename files based on content analysis.
brand-generate
Generate an on-brand document from a saved Brand Profile.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
convert
Convert a file to Markdown using markitdown.