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 pedrol-cmd/brain-drin --skill drin-monolith-to-microservicegit clone --depth 1 https://github.com/pedrol-cmd/brain-drinWrote 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/pedrol-cmd/brain-drin/drin-monolith-to-microservice)<a href="https://agentmods.dev/skills/pedrol-cmd/brain-drin/drin-monolith-to-microservice"><img src="https://agentmods.dev/badge/skills/pedrol-cmd/brain-drin/drin-monolith-to-microservice/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/pedrol-cmd/brain-drin/drin-monolith-to-microservice"><img src="https://agentmods.dev/badge/skills/pedrol-cmd/brain-drin/drin-monolith-to-microservice.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.00024 | $0.00191 |
| Opus 5 | $0.00012 | $0.00096 |
| Sonnet 5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
drin-monolith-to-microservice 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 7d 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
Monolith to Microservice
Purpose
To enable scalable growth and independent deployment by safely breaking down complex legacy systems.
Methodology (The Strangler Pattern)
- Identify Boundaries: Find bounded contexts using Domain Driven Design (DDD).
- Extract Logic: Move a single capability to a new service.
- Proxy Traffic: Redirect traffic to the new service via Ingress/API Gateway.
- Decommission: Remove the old code once the new service is stable.
Rules
- Don't build "Distributed Monoliths" (tight coupling).
- Database extraction must happen after service logic extraction.
- Every microservice must have its own CI/CD and monitoring.
subagents:
- code-architect
- backend-dev
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.
- 7d ago First seen · 26 lines · 24 tokens per session scan A 554d6c432b4f
drin-monolith-to-microservice is a skill published in the GitHub repository pedrol-cmd/brain-drin (11 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 191 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
salesforce-dx
Expert guidance for Salesforce DX development with modern tooling, source-driven development, and CI/CD best practices.
api-backward-compatibility
The Google AIP-180 guidelines define Google's backward compatibility policy for all Google Cloud APIs. Their taxonomy is the most comprehensive publicly available.
azure-functions
Expert knowledge for Azure Functions development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when wiring Functions to triggers/bindings, Cosmos/SQL/Service Bus, VNet/private…
add-node-sdk
Integrate the Temps Node.js SDKs for server-side platform access, KV storage, and Blob storage. Use when the user wants to: (1) Call the Temps platform API from Node.js (deployments, projects, analytics, session replay, etc.), (2) Use Temps KV (key-value) storage, (3) Use Temps Blob storage for files, (4) Server-side…
dxkit-flow
Configure, diagnose, and repair the dxkit UI→API integration gate — set up flow gating, explain the flow-contract diagnosis, fix a net-new broken integration a guardrail flagged, and run the cross-repo handshake. Use when the user says "set up the flow gate", "why is this call unresolved", "the guardrail says I broke…