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.statusgit 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.status)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.status"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.status.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.01910 |
| Opus 5 | $0.00000 | $0.00955 |
| Sonnet 5 | $0.00000 | $0.00382 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
acp.status 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: status
🤖 Agent Directive: If you are reading this file, the command
@acp-statushas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 1.0.0 Created: 2026-02-16 Last Updated: 2026-02-16 Status: Active Scripts: None
Purpose: Display current project status including milestone progress, current task, recent work, and next steps Category: Workflow Frequency: As Needed
What This Command Does
This command provides a comprehensive overview of the current project status by reading agent/progress.yaml and presenting key information in an organized format. It shows where the project stands, what's been accomplished recently, and what needs to be done next.
Use this command when you need to quickly understand the current state of the project without performing a full initialization. It's ideal for checking progress during a session, before starting new work, or when reporting status to stakeholders.
Unlike @acp-init which performs a full context load and updates documentation, @acp-status is a read-only operation that simply reports the current state as recorded in progress tracking.
Prerequisites
- ACP installed in project
-
agent/progress.yamlexists and is up to date
Steps
1. Read Progress Tracking
Read the agent/progress.yaml file to get current project state.
Actions:
- Open and parse
agent/progress.yaml - Extract key information: current milestone, current task, progress percentages
- Note any errors or missing data
Expected Outcome: Progress data loaded successfully
2. Display Current Milestone
Show the current milestone information.
Actions:
- Display milestone ID and name
- Show milestone progress percentage
- Show tasks completed vs total tasks
- Display milestone status (not_started, in_progress, completed)
Expected Outcome: User sees current milestone summary
3. Display Current Task
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 · 294 lines · 0 tokens per session scan A 8297e1795215
acp.status 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,910 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.
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.