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 dependency-mappinggit 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/dependency-mapping)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/dependency-mapping"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/dependency-mapping.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.1 | $0.00077 | $0.00415 |
| Opus 5 | $0.00039 | $0.00208 |
| Sonnet 5 | $0.00015 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
dependency-mapping 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 6d 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
Dependency Mapping (cross-boundary tracing)
Goal: produce the exact chain of components a flow or change touches, so nothing downstream is missed. In a message-driven system, follow the routing keys, not just function calls.
Method
- Start from
.claude/context/SERVICE-MAP.md(the "In → Out" columns give the spine). - For each hop, confirm in code: producer's
publish/routing key → the consumer whose config binds that key → its handler. Use the shared-modelsCLAUDE.mdcontract index to resolve names. - Note every store touched (DB table, graph edge, object-store key) and every API (HTTP route, gRPC RPC).
- Flag the cross-service contracts that break silently if changed (object-store key shape, record field names, routing keys, shared DB columns).
Output (structured, hand to investigator/architect)
FLOW: <name>
HOPS: svc → (routingKey) → svc → ... [each with file:line]
STORES: <DB tables / graph edges / object-store keys touched>
APIS: <HTTP routes / RPCs>
SHARED CONTRACTS AT RISK: <list>
UNKNOWNS: <what you could not confirm in code>
Don't
- Don't assume the SERVICE-MAP diagram is current if code disagrees — report the drift.
- Don't stop at the first service; a "fix" in one hop often needs the consumer updated too.
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.
- 6d ago First seen · 30 lines · 77 tokens per session scan A 197f26a669d4
dependency-mapping is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 415 once invoked, about $0.0004 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-01.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
axiom-networking
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, connection diagnostics.