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-referencegit 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-reference)<a href="https://agentmods.dev/commands/prmichaelsen/gcloud-mcp/acp.design-reference"><img src="https://agentmods.dev/badge/commands/prmichaelsen/gcloud-mcp/acp.design-reference.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.03429 |
| Opus 5 | $0.00000 | $0.01715 |
| Sonnet 5 | $0.00000 | $0.00686 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
acp.design-reference 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive: design-reference
🤖 Agent Directive: This is a SHARED DIRECTIVE, not a user-invocable command. It is referenced by
@acp.task-create,@acp.plan(via task-create delegation), and@acp.proceedto discover and cross-reference design documents, ensuring tasks contain all implementation detail.Do NOT invoke this directive directly. It is called internally by commands that need design document context.
If you are a command reading this file, follow the steps below to discover relevant design documents, extract actionable elements, and return them to the calling command.
Namespace: acp Version: 1.0.0 Created: 2026-03-07 Last Updated: 2026-03-07 Status: Active Scripts: None
Purpose: Discover and cross-reference design documents to ensure tasks have complete implementation detail Category: Workflow (Internal Directive) Frequency: Called by task-create and proceed when design context is needed
Arguments
These arguments are passed as context from the calling command. The directive uses them to determine search scope.
| Input | Source | Description |
|---|---|---|
topic_keywords |
Calling command | Keywords extracted from task name, milestone name, or user description |
milestone_name |
Calling command | Current milestone name (optional, improves search accuracy) |
user_description |
Calling command | User's description of the task or feature (optional) |
draft_content |
Calling command | Draft file content if provided (optional) |
The directive combines these inputs to form a search query. More inputs produce better matches.
What This Directive Does
This directive dynamically discovers design documents relevant to the current task or feature, reads them, extracts all actionable implementation elements, and returns them to the calling command. The calling command uses these elements to generate self-contained tasks or to load supplementary context during implementation.
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 · 356 lines · 0 tokens per session scan A 43b7873b0b54
acp.design-reference 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,429 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
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
template-ui
Design a Sent template-builder interface.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
review
執行 Figma vs 網頁的視覺比對審查，產出像素級 diff 報告和 AI 視覺判斷。.