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 OneDro1d/dark-factory --skill service-mappergit clone --depth 1 https://github.com/OneDro1d/dark-factoryWrote 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/onedro1d/dark-factory/service-mapper)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/service-mapper"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/service-mapper/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/onedro1d/dark-factory/service-mapper"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/service-mapper.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.00103 | $0.02132 |
| Opus 5 | $0.00051 | $0.01066 |
| Sonnet 5 | $0.00021 | $0.00426 |
| Haiku 4.5 | $0.00010 | $0.00213 |
Grade A, and why
service-mapper scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
grep -rn "axios\|fetch(\|http.Get\|http.Post\|requests.get\|requests.post\|HttpClient" --include="*.ts" --include="*.go" --include="*.py" How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Mapper
Analyze a codebase and produce a structured, AI-agent-friendly service map. The output documents every microservice, how they communicate, what databases and tables they own, and what external systems they integrate with.
When to Use
- Onboarding to an unfamiliar codebase
- Generating or updating a CLAUDE.md or SERVICE-MAP.md
- Before planning a new feature (understand what exists)
- Auditing service boundaries and ownership
- Detecting architectural violations (shared DBs, direct HTTP between services, etc.)
- After significant refactoring to verify the architecture still makes sense
Workflow
Execute these steps in order. Each step builds on the previous.
Step 1: Identify Service Boundaries
Scan the repository structure to find all deployable units (services, workers, lambdas, cron jobs).
What to look for:
| Signal | Examples |
|---|---|
| Entrypoints | main.go, main.ts, index.ts, app.py, Program.cs, main.rs |
| Build configs | Dockerfile, docker-compose.yaml, serverless.yml, app.yaml |
| Package manifests | package.json, go.mod, Cargo.toml, pom.xml, *.csproj |
| Deployment specs | K8s manifests, Terraform, Helm charts, DO app specs |
| Monorepo markers | packages/, services/, apps/, cmd/, internal/ |
For each service, record:
- Name
- Language / framework
- Entrypoint file
- Port (if HTTP)
- Type:
webservice|worker|cron|lambda|gateway
Step 2: Map Inter-Service Communication
For each service, trace how it talks to other services.
Communication patterns to detect:
| Pattern | How to Find |
|---|---|
| REST / HTTP | Look for HTTP client calls, fetch, axios, http.Get, base URLs pointing to other services |
| Message bus (RabbitMQ, Kafka, NATS, SQS) | Look for publish, subscribe, consume, queue names, exchange declarations, topic subscriptions |
| gRPC | Look for .proto files, gRPC client/server setup, grpc.Dial |
| Shared library / SDK | Look for internal packages imported across services (e.g., DatabaseClient, shared types) |
| Direct function calls | In monoliths or tightly coupled services — function imports across module boundaries |
| Event contracts | Shared schema definitions (Zod, Protobuf, Avro, JSON Schema) that define inter-service messages |
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.
- 9d ago First seen · 211 lines · 103 tokens per session scan A 6f9d681029fc
service-mapper is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 2,132 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.