What is df-context-store?

A setup process for placing a reusable agent workspace inside a code repository. The workspace contains project maps, shared decisions, specialist agents, hand-off rules, and checks before commits.

Use it when preparing a repository for repeated agent-assisted development or refreshing its project context. It builds the maps from the actual codebase, including services, databases, queues, APIs, and data flows.

It prevents every coding session from re-discovering the same architecture and project rules. It also makes hand-offs between agents checkable and keeps unverified work from being committed.

df-context-store — Skill for Claude Code by OneDro1d

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-context-store

Clone the repo

git clone --depth 1 https://github.com/OneDro1d/dark-factory

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-context-store/github.svg)](https://agentmods.dev/skills/onedro1d/dark-factory/df-context-store)

Your own site

<a href="https://agentmods.dev/skills/onedro1d/dark-factory/df-context-store"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-context-store/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/onedro1d/dark-factory/df-context-store"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-context-store.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,313 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.

Model	Per session	Once invoked
Fable 5.1	$0.00114	$0.01313
Opus 5	$0.00057	$0.00656
Sonnet 5	$0.00023	$0.00263
Haiku 4.5	$0.00011	$0.00131

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

Security

Grade A, and why

df-context-store 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 8d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (substrate-template/dotclaude/hooks/ensure-gate.sh, substrate-template/dotclaude/skills/contract-check/check_contract_test.py, substrate-template/dotclaude/skills/contract-check/check_contract.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-context-store/SKILL.md · 77 lines

How it starts

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

df-context-store — plant the inner-loop substrate (DF Stage 0.5)

Goal: give the repo a persistent, in-repo, read-first agent substrate so analysis is done once and reused, hand-offs can't silently degrade, and nothing ships unverified. This is the inner-loop complement to the heavy DF build stages — the build injects rigor at the seams; this is what lives in the repo and binds every future session. It runs between Stage 0 (Frame) and Stage 1 (PO), and again on demand to refresh.

Template (source of truth): the substrate-template/ directory bundled alongside this skill (skills/df-context-store/substrate-template/).

Procedure

Emit the payload. Copy substrate-template/dotclaude/ into the target repo as .claude/ (agents + context store + hooks/ + contract-check + commit-sync
- AGENT-CONTRACTS.md). Don't overwrite an existing populated store — merge.
Populate from source, don't invent.
- .claude/context/SERVICE-MAP.md — the structural map (services/db/queue/API + flows), generated from the real codebase (use service-mapper).
- .claude/context/DATA-FLOW.md — the data-transform view: data nodes (schema/origin/authority/class), the transform graph (pure|effect), and the validation rules (LOCAL reject / GLOBAL reconcile). Populate nodes + authority from source; leave rules you can't yet cite as marked skeletons.
- Leave FINDINGS.md/DECISIONS.md as clean skeletons that accumulate as the repo is worked. Fill per-service <service>/CLAUDE.md stubs only where verified (file:line).
Wire the always-on carrier. Merge substrate-template/CLAUDE-stanza.md into the repo's root CLAUDE.md (read-first/dispatch/verify rules) — this is what binds every session, not the one-time scaffold.
Arm the lockstep gate + make it self-arming (the every-commit half). The gate can't drift code from the context store silently:
- chmod +x .claude/hooks/pre-commit .claude/hooks/ensure-gate.sh
- Self-arm carrier: merge the SessionStart hook from substrate-template/dotclaude/settings.json into the repo's .claude/settings.json (create it if absent; if it exists, add the SessionStart entry — do not clobber existing hooks). This runs ensure-gate.sh on every session so a fresh clone activates the gate with no manual step. (core.hooksPath is local git config and never travels in a commit — the SessionStart hook is what carries the every-clone half.)
- Arm it now (non-destructive): if the repo has no existing core.hooksPath and no husky, run git config core.hooksPath .claude/hooks (or just run bash .claude/hooks/ensure-gate.sh, which does exactly this safely). If one already exists, do not overwrite it — install the gate as .claude/hooks/pre-commit.local under the existing path (it chains). Say which path you took.
Verify (acceptance). Run bash substrate-template/verify-substrate.sh (from this skill dir) against the template, and for an emitted repo confirm: required files present, no leftover template placeholders in SERVICE-MAP/DATA-FLOW (they're populated), the contract-check suite is green, the gate is executable + actually blocks an undocumented structural change, and the CLAUDE.md stanza is merged. Green is the bar; report the literal check counts.

Read the full file on GitHub · 77 lines

Files

What ships with it

32 files 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.

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.

8d ago First seen · 77 lines · 114 tokens per session scan A 8f02bde802a3

Subscribe to this mod's changes

df-context-store is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 114 tokens to every session and 1,313 once invoked, about $0.0006 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.

Building agents Claude Code Memory and context agent-skills mcp

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

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

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens