Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/mfmezger/ai_agent_dotfiles/agent-registry)<a href="https://agentmods.dev/commands/mfmezger/ai_agent_dotfiles/agent-registry"><img src="https://agentmods.dev/badge/commands/mfmezger/ai_agent_dotfiles/agent-registry.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.05284 |
| Opus 5 | $0.00000 | $0.02642 |
| Sonnet 5 | $0.00000 | $0.01057 |
| Haiku 4.5 | $0.00000 | $0.00528 |
Grade A, and why
agent-registry 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 6d 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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Cloud Agent Registry Skill
Help users interact with the gcloud alpha agent-registry API by translating natural language into the correct gcloud command, showing it for approval, then executing it.
Workflow
-
Resolve session context — at the start of each session, silently run:
gcloud config get-value project 2>/dev/null gcloud config get-value compute/region 2>/dev/nullStore the results as
SESSION_PROJECTandSESSION_LOCATION. Use these as defaults. -
Parse the user's request to identify the resource and action.
-
Construct the gcloud command using session defaults.
-
Approval:
- For
listanddescribecommands: Skip explicit approval and execute immediately. - For
create,delete, orupdatecommands: Show the command and ask for approval: "Ready to run this command? (yes/no)"
- For
-
Execute and display the output.
Auth & Setup
# Check auth
gcloud auth list
# Login
gcloud auth login
# Set project
gcloud config set project PROJECT_ID
# (Optional) Set API override if needed
gcloud config set api_endpoint_overrides/agentregistry https://agentregistry.googleapis.com/
IAM Permissions
| Role | Access Level |
|---|---|
roles/agentregistry.admin |
Full administrative access |
roles/agentregistry.editor |
Editor access |
roles/agentregistry.viewer |
Read only access |
Resource Types & Registration
The primary command for registering resources is gcloud alpha agent-registry services create.
1. MCP Servers
Used to register Model Context Protocol servers.
# Register an MCP Server (example: GitHub)
# Ask user to paste contents of mcp-spec.json for --mcp-server-spec-content
gcloud alpha agent-registry services create github \
--location=us-central1 \
--display-name="GitHub MCP Server" \
--description="Connects to GitHub" \
--mcp-server-spec-type=tool-spec \
--mcp-server-spec-content='PASTE_MCP_SPEC_JSON_HERE' \
--interfaces='[{"protocolBinding": "jsonrpc", "url": "https://api.github.com/mcp"}]'
# List MCP Servers
gcloud alpha agent-registry mcp-servers list --location=us-central1
# Filter MCP Servers by Runtime
gcloud alpha agent-registry mcp-servers list \
--location=us-central1 \
--filter="attributes.\"agentregistry.googleapis.com/system/RuntimeReference\".uri:reasoningEngine"
# List Global MCP Servers
gcloud alpha agent-registry mcp-servers list --location=global
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.
- 6d ago First seen · 444 lines · 0 tokens per session scan A 8661bd7316dc
agent-registry is a command published in the GitHub repository mfmezger/ai_agent_dotfiles (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,284 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
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
harness
Take one harness from "wired" to "the agent is visibly smarter for it".
step-research
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
research
Research a technical or product question.
hello-stranger
Say hello stranger.