dark-factory
v0.1.0Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the GitHub MCP server, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implements and runs the repository's own checks, gets the diff reviewed by an Opus diff-reviewer subagent (each loop capped at 3 rounds, enforced by a hook), and publishes through Curie's built-in approval-gated publication tool within the 10800 second (3 hour) execution bound.
By CurieTechLicense: Apache-2.035 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 26, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install dark-factory for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dark-factory@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/curie-eng/curieClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is examples/dark-factory/.
Plugin files
├── .claude-plugin/plugin.json├── skills/implement-issue/SKILL.md└── .mcp.json
Included Skills1
Turn one labelled GitHub issue into one reviewed pull request, or stop with a stated reason. Use for every factory run; the message is a link to the issue.
MCP servers1
- command
- mcp-server-github
- env.GITHUB_PERSONAL_ACCESS_TOKEN
- ${GITHUB_PERSONAL_ACCESS_TOKEN}
Plugin manifests1
{
"name": "dark-factory",
"version": "0.1.0",
"description": "Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the GitHub MCP server, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implements and runs the repository's own checks, gets the diff reviewed by an Opus diff-reviewer subagent (each loop capped at 3 rounds, enforced by a hook), and publishes through Curie's built-in approval-gated publication tool within the 10800 second (3 hour) execution bound.",
"author": {
"name": "CurieTech"
},
"license": "Apache-2.0",
"keywords": [
"factory",
"coding",
"github",
"issues",
"pull-request"
],
"secrets": [
"GITHUB_PERSONAL_ACCESS_TOKEN"
],
"starterPrompts": [
"https://github.com/acme-corp/acme-bot/issues/1"
],
"toolPolicy": {
"enforcement": "curie/mcp-tool-policy@1",
"allow": [
"github/get_issue",
"github/add_issue_comment"
],
"approvalRequired": [],
"deny": []
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[dark-factory on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dark-factory)