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 instructions/dubsopenhub/dark-factory/copilot-instructionsgit clone --depth 1 https://github.com/DUBSOpenHub/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/instructions/dubsopenhub/dark-factory/copilot-instructions)<a href="https://agentmods.dev/instructions/dubsopenhub/dark-factory/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/dubsopenhub/dark-factory/copilot-instructions.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.00680 | $0.00680 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
dark-factory copilot-instructions.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — Dark Factory
This repository contains Dark Factory, a GitHub Copilot CLI skill that orchestrates an agent pipeline with sealed-envelope testing and cross-family model independence (Shadow Score Spec v2.0, Level 4 — Adversarial Independence).
File map
| File/Dir | Purpose |
|---|---|
SKILL.md |
Factory Manager orchestrator prompt (the brain) |
agents/*.md |
8 specialist agent prompts |
templates/*.md |
Artifact output formats |
protocols/sealed-envelope.md |
Isolation invariants |
protocols/model-independence.md |
Why cross-family separation is required |
protocols/checkpoint-gate.md |
Autonomy modes + quality gates |
config.yml |
Tunables (invariants, families, capabilities, roles, gates, thresholds) |
catalog.yml |
Skill metadata + file references |
.github/scripts/validate_conformance.py |
Level 4 conformance check (CI) |
docs/TESTING.md |
Playbooks + QA checklist |
docs/ADR.md |
Why these decisions |
Non-negotiables
- Sealed envelope is sacred. The Lead Engineer must never see sealed tests; the QA Sealed agent must never see code. Isolation is filesystem topology (vault outside the repo, disposable verify worktree), not prompt wording.
- Model independence is sacred. Seal author and implementer must be in different families. Same-family pairing biases every Shadow Score toward 0% — it overclaims quality. Phase 0 aborts on violation.
- Config is the source of truth. Never hardcode model names or tunables inside prompts.
- Agent prompts <= 200 lines. If a prompt grows, split responsibilities instead.
- Just a skill. Do not add runtime code, package managers, telemetry, dashboards, or plugin systems. The one exception is
.github/scripts/validate_conformance.py, which runs in CI only and must stay dependency-light. - Worktree isolation. All build work happens under
.factory/until delivery approval. - Delivery is always human-approved, in every autonomy mode including
dark.
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.
- 5d ago First seen · 49 lines · 680 tokens per session scan A 85f7cf267fbd
dark-factory copilot-instructions.md is an instructions file published in the GitHub repository DUBSOpenHub/dark-factory (25 stars, last pushed 1mo ago), licensed MIT. It adds 680 tokens to every session, about $0.0034 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-08-30.
Other instructions, from other repositories
agent-framework copilot-instructions.md
Copilot instructions for microsoft/agent-framework, covering github copilot instructions, repository structure and architectural decision records (adrs).
agent-framework python.instructions.md
Instructions for microsoft/agent-framework: See AGENTS.md for project structure and package documentation. Detailed conventions are in the agent skills under .github/skills/.
graph-engineering-architectures AGENTS.md
Instructions for Mark393295827/graph-engineering-architectures, covering graph engineering architectures - agent instructions, scope, change contract and required checks.
isomux AGENTS.md
AGENTS.md instructions for nmamano/isomux, covering isomux, how to develop, formatting and linting, key decisions (do not revisit) and project layout.
Starlight-Intelligence-System AGENTS.md
AGENTS.md instructions for frankxai/Starlight-Intelligence-System, covering frank dna, standards, multi-agent systems & agent harnesses, 1. what makes sis unique and 2. the swarm harness process.
github-azure-agentic-journeys AGENTS.md
Instructions for DanWahlin/github-azure-agentic-journeys, covering agents and skills, journeys, prerequisites, agent & skill system and available agents.