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 sarveshtalele/mcp-skills-registry --skill topology-planninggit clone --depth 1 https://github.com/sarveshtalele/mcp-skills-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/sarveshtalele/mcp-skills-registry/topology-planning)<a href="https://agentmods.dev/skills/sarveshtalele/mcp-skills-registry/topology-planning"><img src="https://agentmods.dev/badge/skills/sarveshtalele/mcp-skills-registry/topology-planning/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/sarveshtalele/mcp-skills-registry/topology-planning"><img src="https://agentmods.dev/badge/skills/sarveshtalele/mcp-skills-registry/topology-planning.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.00050 | $0.00482 |
| Opus 5 | $0.00025 | $0.00241 |
| Sonnet 5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
topology-planning 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.
What it actually says
topology-planning
Turn a discovery summary into a target architecture and a phased, low-risk migration plan with ADRs.
When to use
After legacy-discovery, when defining the target state. Triggers: target
architecture, migration plan, topology, modernization plan.
Inputs
discovery_summary(string, required) — summary of the current system.target_style(string, optional) —microservices|modular-monolith|serverless.
Outputs
migration_plan_markdown— principles, ADRs, phased plan, risk table.phases— ordered phase objects{id, name, goal}.
How it works
Selects a principle set for the chosen style and assembles a strangler-fig migration across four phases with a risk/mitigation table.
User stories
- As an architect, I get a defensible target architecture and an incremental path, not a big-bang rewrite.
Edge cases
- Unknown
target_style→ defaults tomicroservices. - Empty summary → plan still renders with prompts to fill in.
Files
See DOCS.md.
What ships with it
7 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.
- 12d ago First seen · 67 lines · 50 tokens per session scan A 0799105d3a39
topology-planning is a skill published in the GitHub repository sarveshtalele/mcp-skills-registry (2 stars, last pushed 11d ago), licensed MIT. It adds 50 tokens to every session and 482 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-31.
Other skills, from other repositories
llama-factory
Expert guidance for fine-tuning LLMs with LLaMA-Factory - WebUI no-code, 100+ models, 2/3/4/5/6/8-bit QLoRA, multimodal support.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
billing-stripe
Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
scope-appropriate-architecture
Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.