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.
git clone --depth 1 https://github.com/maton-ai/api-gateway-skillWrote 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/plugins/maton-ai/api-gateway-skill/plugin)<a href="https://agentmods.dev/plugins/maton-ai/api-gateway-skill/plugin"><img src="https://agentmods.dev/badge/plugins/maton-ai/api-gateway-skill/plugin/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/plugins/maton-ai/api-gateway-skill/plugin"><img src="https://agentmods.dev/badge/plugins/maton-ai/api-gateway-skill/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
api-gateway 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 1mo 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.
What it actually says
{
"name": "api-gateway",
"description": "API gateway for calling third-party APIs with managed auth.",
"version": "1.0.0",
"author": {
"name": "Maton",
"url": "https://maton.ai"
},
"homepage": "https://maton.ai",
"repository": "https://github.com/maton-ai/api-gateway-skill",
"license": "MIT",
"keywords": [
"maton",
"api",
"gateway",
"automation",
"integrations"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 173 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 20 lines scan A 063b5f79dd0a
api-gateway is a plugin published in the GitHub repository maton-ai/api-gateway-skill (33 stars, last pushed 14d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
data-validation-suite
Schema validation, data quality monitoring, streaming validation pipelines, and input validation for backend APIs.
distributed-debugging
Distributed system tracing and debugging across microservices.
documentation-generation
OpenAPI specification generation, Mermaid diagram creation, tutorial writing, API reference documentation.
functional-programming
Functional programming with Elixir, OTP patterns, Phoenix framework, and distributed systems.
spring-boot
Domain-Driven Design with Spring Boot 4 (DDD patterns, Spring Data, REST APIs, Spring Modulith).
api-documentation
Generate interactive API documentation.