What is dark-factory?

A GitHub workflow that moves ready issues through development, automated checks, review, and merging. It offers an autonomous mode where sub-agents handle the work and an interactive mode where a human collaborates with the agent.

Running ready GitHub issues from implementation through review and merge, while following branch protection and the team's project-board settings.

It reduces the manual coordination needed to move multiple issues through a team's normal GitHub safeguards. The human can choose whether to supervise the process or participate directly.

dark-factory — Skill for Claude Code by ebizsoft/agentic-claude-code

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 ebizsoft/agentic-claude-code --skill dark-factory

Clone the repo

git clone --depth 1 https://github.com/ebizsoft/agentic-claude-code

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/ebizsoft/agentic-claude-code/dark-factory/github.svg)](https://agentmods.dev/skills/ebizsoft/agentic-claude-code/dark-factory)

Your own site

<a href="https://agentmods.dev/skills/ebizsoft/agentic-claude-code/dark-factory"><img src="https://agentmods.dev/badge/skills/ebizsoft/agentic-claude-code/dark-factory/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/ebizsoft/agentic-claude-code/dark-factory"><img src="https://agentmods.dev/badge/skills/ebizsoft/agentic-claude-code/dark-factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,695 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.00210	$0.01695
Opus 5.5	$0.00084	$0.00678
Sonnet 5.5	$0.00042	$0.00339
Haiku 4.5	$0.00021	$0.00169

Measured 2mo ago against content hash 9f92e1536e8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dark-factory 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 2mo ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/catchup.sh, scripts/lib.sh, scripts/listener.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/dark-factory/SKILL.md · 104 lines

How it starts

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

dark-factory — one pattern, two modes

This skill runs the Dark Factory GitHub-orchestration pattern. There is one command, two modes — pick by how the human participates:

Mode	Invocation	Who does the work	Human's role
Autonomous (default)	`/dark-factory [issue]`	Claude (team-lead) spawns a swarm of sub-agents that develop, verify, review, and merge each Ready issue end-to-end	Authorizes merges; watches the board. The factory runs itself.
Interactive	`/dark-factory --interactive`	Claude is one peer developer on a human crew — authors PRs, reviews teammates' PRs	Reviews, approves, merges, collaborates over Teams. The human plays a part in the factory.

Both modes are the same conceit — issues flowing through dev → review → merge behind GitHub-native gates — at two autonomy levels. Don't blend them in one run.

Always do first (both modes)

Read config/team.json — repos, your identity (.self.github), roster (.members), board (.board), base branches (.base_branches), policy, and the autonomous-mode constants (.board.project_id / .status_field_id / .status_options, .autonomous.*). scripts/lib.sh exposes most of it to the shell.
Credential & scope preflight — run bash scripts/preflight.sh <autonomous|interactive> and read the report before doing any work. It proves, by making real read-only API calls (not by trusting declared scopes), that gh is authenticated and the token actually has the capabilities this run needs: repo write on every .repos repo, Projects v2 access for board moves (autonomous), webhook admin for the listener, and the opt-in teams CLI when comms are on. gh auth login's default scopes include neither project nor admin:repo_hook, so board moves and webhook registration fail silently without it. If it prints RESULT: FAIL, STOP and give the user the exact remediation it emits (usually a gh auth refresh -h github.com -s … line) — do not boot the factory on credentials that don't work. RESULT: OK (with warnings) is safe to proceed; each ⚠ has a documented fallback — note them in your summary.
source scripts/lib.sh — gives you REPOS, base_branch <repo>, notify_all / notify_subset / notify_user, request_reviews.sh, webhook helpers.
Read reference/budget.md — the REST-vs-GraphQL rate discipline. It governs every gh call in either mode; the factory has run the GraphQL pool to zero before. Not optional.
Read reference/verification.md — the Iron Law: no completion claim ("done / green / passing / clean") without fresh verification evidence. It governs every board move, agent report, and gh pr create / merge / approve, and is enforced at the PR boundary by the verify-before-completion hook.
Worktree discipline (any code change): one worktree per task at /tmp/wt-<issue>, branched off fresh origin/<base>, its own dependency install; never work in the main checkout; remove it after merge. (Full rules in the mode docs.)

Read the full file on GitHub · 104 lines

Files

What ships with it

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

2mo ago First seen · 104 lines · 210 tokens per session scan A 9f92e1536e8f

Subscribe to this mod's changes

dark-factory is a skill published in the GitHub repository ebizsoft/agentic-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 210 tokens to every session and 1,695 once invoked, about $0.0008 per session on Opus 5.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-31.

Git and workflow Project management

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

prowler-commit

Creates professional git commits for Prowler following conventional-commits format, with prek pre-commit hooks. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 44 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens