df-infrastructure

df-infrastructure is a skill for Claude Code, Codex from OneDro1d/dark-factory. It costs 64 tokens per session (605 once invoked), scanned A, original, Apache-2.0.

An infrastructure guide for deciding where an application runs, where its data is stored, and how access between parts is enforced. It also defines the visible monitoring and logging setup needed to operate the system.

In plain words
What is it for?
Use it to plan deployments across development, testing, acceptance, and production environments; configure storage, regions, permissions, secrets, network rules, dashboards, and alerts.
Why use it?
It prevents unclear data placement, misplaced trust between services, unmanaged secrets, and monitoring that exists but cannot be viewed or verified.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan deployments across development, testing, acceptance, and production environments; configure storage, regions, permissions, secrets, network rules, dashboards, and alerts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/onedro1d/dark-factory/df-infrastructure
Install

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.

Any agent
npx skills add OneDro1d/dark-factory --skill df-infrastructure
Clone the repo
git clone --depth 1 https://github.com/OneDro1d/dark-factory

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for df-infrastructure

README.md
[![agentmods](https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-infrastructure/github.svg)](https://agentmods.dev/skills/onedro1d/dark-factory/df-infrastructure)
Your own site
<a href="https://agentmods.dev/skills/onedro1d/dark-factory/df-infrastructure"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-infrastructure/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.

agentmods 80×15 button for df-infrastructure

Your own site · 80×15
<a href="https://agentmods.dev/skills/onedro1d/dark-factory/df-infrastructure"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-infrastructure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 605 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00605
Opus 5 $0.00032 $0.00302
Sonnet 5 $0.00013 $0.00121
Haiku 4.5 $0.00006 $0.00060

Measured 9d ago against content hash 6d9e3d7a191c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

df-infrastructure 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 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.

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.

skills/df-infrastructure/SKILL.md · 31 lines

How it starts

The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dark Factory — Infrastructure Architect (where data lives + the boundaries)

Overview

Infra decides where the architecture runs and makes it deployable across all environments. It produces one must-have output: the Deployment & Infrastructure Spec. Through the lens (df-data-transform-lens): Infra places the data nodes and draws the boundaries. Runs in parallel with the Developer lane.

When to use

Deploying across DTAP, provisioning clusters/secrets/network/storage, wiring observability sinks + operational knobs, or enforcing runtime trust.

What Infra does

  • location per data node → storage class, region, residency. The governance tag (PHI/PII, residency) is enforced by where you put the data.
  • Every unit edge is a trust boundary. "Inside the cluster is trusted" is the sticky-trust anti-pattern. Secrets/IAM enforce the boundary, not network position. Map every SA runtime-trust entry to a mechanism (IRSA/IAM, sealed-secrets, network policy, DB roles).
  • Build + verify the Observability Surface — stand up the dashboards + datasources + log/trace sinks and verify they render live data (the acceptance bar; see df-observability). Ship dashboards as code (deployments/grafana/…), not hand-clicked.
  • Provision every operational knob the Ops runbook + reconciliation + effect-compensation paths will need.

Reversibility (the autonomy gate)

Building manifests is reversible and high-autonomy; applying them to production is irreversible → a human gate regardless of how green the evidence is (see df-adversary-gate / the two-axis autonomy model). A production change requires a ticket + announcement.

Instructions

  1. Start from the platform's standard environment progression (Dev → Test → Acceptance → Production), base + overlays. Record per-product deltas only.
  2. Map every SA runtime-trust entry → enforcement; every observability entry → a sink; every knob → a provisioning step.
  3. Verify the dashboards render live data and the $correlationId query returns real cross-service results.
  4. Write the deploy procedure QA follows to stand the system up.

Read the full file on GitHub · 31 lines

Changes

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.

  1. 9d ago First seen · 31 lines · 64 tokens per session scan A 6d9e3d7a191c

Subscribe to this mod's changes

df-infrastructure is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 605 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-09-01.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens