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 agentmods add commands/alphaaiservice/cortex/init-mcp-servergit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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 | $0.00121 | $0.03868 |
| Opus 5 | $0.00060 | $0.01934 |
| Sonnet 5 | $0.00024 | $0.00774 |
| Haiku 4.5 | $0.00012 | $0.00387 |
Grade A, and why
init-mcp-server 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 2d 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init MCP Server — Scaffold a Standalone MCP Server Project
Create: $ARGUMENTS
This command scaffolds a standalone MCP server project — the kind you publish to PyPI/npm and other people install. For MCP servers embedded INSIDE a SaaS app (under app/ai/mcp/ of a FastAPI/NestJS/Spring Boot app), use /auto-build with AI in the FEATURE_PROFILE instead.
📖 CANONICAL REFERENCE:
skills/alpha-architecture/references/CODE_PATTERNS_MCP_SERVER.mdcontains the full library of MCP server patterns (tools/prompts/resources, error handling, JSON-RPC, transport choice, testing). Load that file for all code patterns referenced below.
Step 0: Parse arguments
Extract from $ARGUMENTS:
server-name(required, first positional arg) — kebab-case, e.g.slack-mcp,postgres-mcp. Becomes the project directory + the MCP server name advertised in the handshake.--lang=python(default) |typescript. Python recommended — the official SDK is more mature and the ecosystem is bigger for backend-style MCP servers.--transport=stdio(default) |http|sse.stdiois recommended for almost everything (Claude Code, Claude Desktop, Cursor, etc. all use stdio). Usehttp/sseonly if you specifically need to serve MCP over the network.--with-tools(default ON) — include example tools (the most common MCP primitive).--with-prompts(default OFF) — include example prompts (slash-command-style prompts the host can call).--with-resources(default OFF) — include example resources (URI-addressable read-only content).
If server-name is missing, stop and ask the user for it.
If --lang is missing, ask: "Python (mature SDK, recommended) or TypeScript (better for web-facing MCP)?"
Step 1: Decision tree — should they actually be doing this?
Before scaffolding, confirm the user wants a STANDALONE MCP server, not the embedded variant:
Ask: "Is this MCP server going to be a separate package that other people install
(PyPI / npm), OR is it going to be part of an existing app you're building?"
Standalone package → continue with this command
Inside an existing app → STOP. Use /auto-build or /retrofit instead. The
embedded MCP server lives under app/ai/mcp/ of
the host application; don't create a separate repo.
Not sure yet → recommend standalone. Easy to publish; can also
vendor it into an app later as a submodule.
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.
- 2d ago First seen · 408 lines · 121 tokens per session scan A 6cc2da46246e
init-mcp-server is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 121 tokens to every session and 3,868 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 commands, from other repositories
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
lucius
Segunda opinión técnica externa vía Codex CLI — diagnóstico y prescripción por ítem.
cdd-quick-create
Produce a small, self-contained deliverable — a script plus a README, not a full CDD project: /cdd-quick-create (takes an optional one-line description of what to build).
claude-flow-swarm
Coordinate multi-agent swarms for complex tasks.
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
bootstrap
PACT session-start ritual — identify the session team (platform-provisioned), secretary spawn, paused-state surface, bootstrap marker.