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 skills add mfmezger/ai_agent_dotfiles --skill agent-registrygit clone --depth 1 https://github.com/mfmezger/ai_agent_dotfilesWrote 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/skills/mfmezger/ai_agent_dotfiles/agent-registry)<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/agent-registry"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/agent-registry/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/agent-registry"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/agent-registry.svg" alt="Reviewed on agentmods" width="80" 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.00110 | $0.05428 |
| Opus 5 | $0.00055 | $0.02714 |
| Sonnet 5 | $0.00022 | $0.01086 |
| Haiku 4.5 | $0.00011 | $0.00543 |
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 8d 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 — 463 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 ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 463 lines · 110 tokens per session scan A 2e6b8fdd5d5d
agent-registry is a skill published in the GitHub repository mfmezger/ai_agent_dotfiles (5 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 5,428 once invoked, about $0.0006 per session on Opus 5. 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 skills, from other repositories
cmux-cloud-vm
Route work to cmux Cloud machines (persistent cloud VMs) from the CLI — cmux vm route/run/agent pick a machine for you; vm tree / surface ls show the surface catalog (This Mac and every machine: terminals, VNC screens, browsers) and vm open / surface open put any of them in a pane; plus create, exec, push/pull, ports…
daytona-dev
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.
daytona-cloud-server
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
deploying-infra
Validate infrastructure changes and, after explicit confirmation, apply Terraform, Helm, Kustomize, or Kubernetes deployments. Use when the user says "deploy", "deploy to staging", "terraform apply", "helm upgrade", "kubectl apply", "rollout", "deploy check", "validate deployment", or "validate infrastructure".…
webserver-configuration
Complete web server configuration workflows for Nginx, Apache, Traefik, and Caddy. Use when setting up, configuring, or optimizing web servers, SSL/TLS, load balancers, or reverse proxies.
embedded-dev
Use when developing firmware on ESP32/STM32/RP2040/nRF52, experiencing DMA overflow, SPI timeout, LCD blank display, frame corruption, GPIO conflicts, sensor reading errors, Wi-Fi disconnect, or needing driver configuration, hardware debugging, display/GUI setup, protocol implementation, serial monitoring. Use even if…