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.syncgit 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.sync)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.sync"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.sync.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 | $0.00000 | $0.02265 |
| Opus 5 | $0.00000 | $0.01132 |
| Sonnet 5 | $0.00000 | $0.00453 |
| Haiku 4.5 | $0.00000 | $0.00227 |
Grade A, and why
acp.sync 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 3d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: sync
🤖 Agent Directive: If you are reading this file, the command
@acp.synchas been invoked. Follow the steps below to execute this command.
Namespace: acp Version: 1.1.0 Created: 2026-02-16 Last Updated: 2026-02-18 Status: Active Scripts: None
Purpose: Synchronize documentation with source code by identifying and updating stale documentation Category: Documentation Frequency: As Needed
What This Command Does
This command synchronizes ACP documentation with the actual source code implementation. It reads source files, compares them with design documents and patterns, identifies documentation drift, and updates stale documentation to match reality.
Use this command after making significant code changes, when you suspect documentation is outdated, or periodically to ensure documentation stays current. It's particularly useful after implementing features, refactoring code, or completing milestones.
Unlike @acp.update which updates progress tracking, @acp.sync focuses on keeping design documents, patterns, and technical documentation aligned with the actual codebase.
Prerequisites
- ACP installed in project
- Source code exists to compare against
- Documentation exists in
agent/directory (design, tasks, patterns) - Scripts exist in
agent/scripts/(if applicable) - You have understanding of what changed in code
Steps
1. Read Design Documents
Load all design documents to understand documented architecture.
Actions:
- Read all files in
agent/design/ - Note documented features, patterns, and architecture
- Understand documented API contracts
- Identify documented dependencies
- List documented file structures
Expected Outcome: Documented architecture understood
2. Read Task Documents
Review task documents to understand documented implementation approach.
Actions:
- Read all files in
agent/tasks/ - Note documented implementation steps
- Identify documented tools and dependencies
- Check for code examples in task steps
- List documented functions and approaches
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.
- 3d ago First seen · 365 lines · 0 tokens per session scan A efa3b32f56f6
acp.sync 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,265 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.