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 agentic-community/mcp-gateway-registry --skill generate-agent-cardgit clone --depth 1 https://github.com/agentic-community/mcp-gateway-registryWrote 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/agentic-community/mcp-gateway-registry/generate-agent-card)<a href="https://agentmods.dev/skills/agentic-community/mcp-gateway-registry/generate-agent-card"><img src="https://agentmods.dev/badge/skills/agentic-community/mcp-gateway-registry/generate-agent-card/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/agentic-community/mcp-gateway-registry/generate-agent-card"><img src="https://agentmods.dev/badge/skills/agentic-community/mcp-gateway-registry/generate-agent-card.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.02782 |
| Opus 5 | $0.00025 | $0.01391 |
| Sonnet 5 | $0.00010 | $0.00556 |
| Haiku 4.5 | $0.00005 | $0.00278 |
Grade A, and why
generate-agent-card 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 12d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate A2A Agent Card
Generate an A2A (Agent-to-Agent) protocol agent card JSON file by analyzing the source code at $ARGUMENTS.
Steps
1. Carefully study the source code
Do NOT just skim the top-level files. Agents can be complex, multi-file projects. You MUST thoroughly explore the entire folder structure before generating the card.
If $ARGUMENTS is a local folder path, use Glob to find ALL Python files, YAML/JSON configs, and README files in the folder and its subfolders. Read every relevant file.
If $ARGUMENTS is a GitHub URL, use WebFetch to read the raw file contents. Follow imports to discover additional files.
Where to look (agents are not always a single file):
- Entrypoints:
main.py,app.py,agent_entrypoint.py,server.py,__main__.py - Tool definitions: tools may be in separate files like
tools/,skills/,functions/, or registered via decorators (@tool,@function_tool,@mcp_tool) - Multi-agent setups: look for orchestrator/supervisor patterns, multiple agent classes, agent registries, sub-agent folders
- Prompts and system messages: may be in separate files like
prompts/,templates/,system_prompt.txt, or as string constants - MCP server connections: look for MCP client configs,
mcp_servers,MCPClient, tool imports from MCP servers - these are skills the agent can use - Config files:
pyproject.toml,requirements.txt,.bedrock_agentcore.yaml,agent_config.yaml,docker-compose.yml - Sub-folders: check ALL subdirectories for additional agents, tools, or shared utilities
From the code, detect:
- Agent name: from constants, CLI args, config files, class names
- Description: from docstrings, README, module-level comments
- Skills/tools: from
@tooldecorators, tool lists, function definitions passed to agent frameworks (Strands, LangChain, CrewAI, AutoGen, etc.), MCP tool connections, imported tool modules - Multi-agent skills: if there are multiple agents (orchestrator, sub-agents), each agent's capabilities should be represented as skills
- MCP-sourced tools: if the agent connects to MCP servers, list those tools as skills too (read the MCP server configs to find tool names and descriptions)
- Input/output modes: text, images, files, structured data - check what the agent accepts and returns
- Protocol: HTTP (
HTTP+JSON), A2A (JSONRPC), MCP - Auth mechanism: IAM/SigV4, Cognito/JWT, API key, OAuth2
- Streaming support: from framework config, capabilities flags
- Version: from constants, pyproject.toml, or default to
1.0.0 - Endpoint URL: from
.bedrock_agentcore.yamlor deployment config if available
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.
- 12d ago First seen · 263 lines · 50 tokens per session scan A 4ab8b0807d18
generate-agent-card is a skill published in the GitHub repository agentic-community/mcp-gateway-registry (909 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 2,782 once invoked, about $0.0003 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-30.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.