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 skills/arbazkhan971/godmode/micronpx skills add arbazkhan971/godmode --skill microgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/micro)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/micro"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/micro.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00991 |
| Opus 5 | $0.00004 | $0.00495 |
| Sonnet 5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
micro 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 today.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate When
/godmode:micro, "design microservices"- "decompose this monolith", "service mesh"
- "saga pattern", "inter-service communication"
Workflow
1. System Context
find . -name "docker-compose*" -o -name "*.proto" \
| head -10
grep -r "microservices\|grpc\|moleculer" \
package.json 2>/dev/null
Architecture: Monolith | Modular Monolith | Microservices
Team Structure: <teams, ownership>
Scale: <request volume, data volume>
Data Stores: <databases, caches, brokers>
2. Service Decomposition
Domain-driven bounded contexts. Each service owns its data exclusively. Decompose by business capability (not technical layer).
IF two services need strong consistency: they belong together. IF greenfield: start with modular monolith.
3. Inter-Service Communication
- REST: CRUD, immediate response, external-facing. Circuit breaker (5 failures -> open), timeout 3s, retry 3x exponential, fallback.
- gRPC: high-throughput internal (10K+ RPS), low-latency, streaming, polyglot.
- Event-Driven: eventual consistency, decoupling, fan-out. Kafka (ordered), RabbitMQ (routing), SQS/SNS (AWS), NATS (ultra-low latency).
DECISION: Need immediate response -> sync (REST/gRPC). Fire-and-forget/fan-out -> async (events).
4. Service Mesh
- Istio: complex routing, multi-cluster, WASM. ~128Mi memory per sidecar.
- Linkerd: simpler, lighter (~64Mi), gentler learning curve.
5. Service Discovery
K8s DNS: <svc>.<ns>.svc.cluster.local.
LB: Round Robin (homogeneous), Least Request
(variable latency), Consistent Hash (sticky).
6. Saga Pattern
- Choreography (2-4 services): each publishes events, next reacts. Loose coupling, hard to trace.
- Orchestration (5+ services): central coordinator, compensates in reverse on failure. Easy to trace.
Every step MUST have compensating action (idempotent). Persist saga state. Use correlation IDs. Set timeouts.
7. Resilience Patterns
Circuit Breaker (5 consecutive 5xx, 30s half-open), Timeout (3s default), Retry (3x exponential+jitter), Bulkhead (10 concurrent per svc), Rate Limit, Fallback.
What ships with it
1 file 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.
- today First seen · 131 lines · 8 tokens per session scan A d7ece3a3ec2f
micro is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 991 once invoked, about $0.0000 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
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
biome
Repository guidance for using Biome as the formatter, linter, and code quality tool within the hr-skills monorepo.
dashboard-builder
Build and manage recurring dashboard views of key metrics — set up daily/weekly monitoring with saved metrics and segments. Use when the user wants to create a recurring dashboard, set up KPI monitoring, or establish a baseline.