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/command.templategit clone --depth 1 https://github.com/prmichaelsen/gcloud-mcpWhat 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 | $0.00000 | $0.02210 |
| Opus 5 | $0.00000 | $0.01105 |
| Sonnet 5 | $0.00000 | $0.00442 |
| Haiku 4.5 | $0.00000 | $0.00221 |
Grade A, and why
command.template 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 yesterday.
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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: {command-name}
🤖 Agent Directive: If you are reading this file, the command
@{namespace}-{command-name}has been invoked. Follow the steps below to execute this command. Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} 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: {namespace} Version: 1.0.0 Created: YYYY-MM-DD Last Updated: YYYY-MM-DD Status: [Draft | Active | Deprecated] Scripts: {namespace}.{command-name}.sh, acp.common.sh, acp.yaml-parser.sh
Note: The **Scripts**: field is REQUIRED and must list ALL script dependencies (direct + shared utilities). This must match the scripts array in package.yaml exactly. If the command has no script dependencies, use **Scripts**: None.
Purpose: [One-line description of what this command does] Category: [Workflow | Documentation | Maintenance | Creation | Custom] Frequency: [Once | Per Session | As Needed | Continuous]
Arguments
[If your command accepts arguments, document them here. Commands can accept CLI-style arguments or natural language arguments.]
CLI-Style Arguments (optional):
--flagor-f- Description of what this flag does--option <value>- Description of option that takes a value--another-flag- Another flag description
Natural Language Arguments (optional):
@{namespace}.{command} for specific item- Description@{namespace}.{command} with custom setting- Description
Argument Mapping: Arguments are inferred from chat context. The agent will:
- Parse explicit CLI-style flags if present
- Extract intent from natural language
- Ask for clarification if ambiguous
- Default to interactive mode if unclear
Example:
## Arguments
**CLI-Style Arguments**:
- `--global` or `-g` - Operate on global packages instead of local
- `--verbose` or `-v` - Show detailed output
- `--force` - Skip confirmations and proceed
**Natural Language Arguments**:
- `@acp.package-list global packages` - List global packages
- `@acp.package-list with details` - Verbose mode
**Argument Mapping**:
The agent infers intent from context. "Show me global packages" maps to `--global` flag.
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.
- yesterday First seen · 340 lines · 0 tokens per session scan A 89d74207e14f
command.template 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,210 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.