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/afterlaunch/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/plugins/afterlaunch/mcp/gemini-extension)<a href="https://agentmods.dev/plugins/afterlaunch/mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/afterlaunch/mcp/gemini-extension/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/afterlaunch/mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/afterlaunch/mcp/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
afterlaunch 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 14d 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": "afterlaunch",
"version": "1.0.1",
"description": "The growth record and next move for your product: what the answer engines say about it, what shipped and what it moved, and the next growth move, ranked and briefed.",
"mcpServers": {
"afterlaunch": {
"httpUrl": "https://afterlaunch.io/api/mcp",
"headers": {
"Authorization": "Bearer ${AFTERLAUNCH_API_KEY}"
}
}
},
"settings": [
{
"name": "AfterLaunch API key",
"description": "Bearer key from npx afterlaunch connect or https://afterlaunch.io/app/connect#keys",
"envVar": "AFTERLAUNCH_API_KEY",
"sensitive": true
}
]
}
What ships with it
1 file beside gemini-extension.json 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.
- 14d ago First seen · 22 lines scan A f74c313581f4
afterlaunch is a plugin published in the GitHub repository afterlaunch/mcp (2 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-11-07.
afterlaunch compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| afterlaunchafterlaunch/mcp | Plugin | 2 | 14d ago | MIT | A | — | Gemini CLI |
| digestseo-geoAKzar1el/mcp-geo | Plugin | 40 | today | MIT | A | — | Gemini CLI |
| digestseo-geoAKzar1el/mcp-geo | Plugin | 40 | today | MIT | A | — | Claude Code |
| open-geoPupok462/open-geo | Plugin | 30 | 28d ago | MIT | A | — | Claude Code |
| claude-rankHouseofmvps/claude-rank | Plugin | 150 | 4mo ago | MIT | A | — | Claude Code |
| aeo-brand-scanWannabDad/aeo-brand-scan | Plugin | 3 | 6mo ago | MIT | A | — | Claude Code |
| crazyseod08m/crazyseo | Plugin | 4 | 3mo ago | AGPL-3.0 | A | — | Claude Code |