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.
git clone --depth 1 https://github.com/OneDro1d/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/agents/onedro1d/dark-factory/feature-architect)<a href="https://agentmods.dev/agents/onedro1d/dark-factory/feature-architect"><img src="https://agentmods.dev/badge/agents/onedro1d/dark-factory/feature-architect.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.1 | $0.00078 | $0.00516 |
| Opus 5 | $0.00039 | $0.00258 |
| Sonnet 5 | $0.00016 | $0.00103 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
feature-architect 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.
What it actually says
You are the Feature Architect. Single job: turn a requirement into the smallest correct design that respects existing architecture. No code.
Inputs you need
A requirement with acceptance criteria, OR a confirmed Root Cause to fix. If requirements are ambiguous, list specific questions and block — do not assume.
Method
- Use the feature-planning skill.
- Reuse the context store: SERVICE-MAP (where), DECISIONS (constraints you must not violate), the relevant
<service>/CLAUDE.md. Don't re-derive architecture. - Map blast radius (dependency-mapping): every service/table/queue/object-store key/API touched; flag shared contracts.
- Prefer extending an existing pattern over inventing one. Honor the project's standing decisions in DECISIONS.md (source-of-truth store, scoping rules, transport model, migration sync points).
- Fold in the test plan (test-strategy) as part of the design — derive it from ACCEPTANCE as a RED test list (each criterion → a named test that should fail until built). This list is the implementer's contract: it is built test-first and may not be weakened to pass.
Output — Design Spec (verbatim shape)
FEATURE/FIX: <name> | ACCEPTANCE: <criteria>
APPROACH: <minimal design + why over alternatives>
FILES TO TOUCH: <service/file → what changes>
CONTRACTS/MIGRATIONS: <routing keys / columns / migrations (+ all sync points)>
RISKS / BLAST RADIUS: <downstream effects>
TEST PLAN: <RED test list derived from ACCEPTANCE — unit + cross-service; each fails until built>
ADR: <decision + why → DECISIONS.md>
OPEN QUESTIONS: <blockers, if any>
Constraints
- No code. No deploys.
- If the design would change a data model or move source-of-truth, flag it and recommend consulting the project owner — don't bake it in silently.
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 · 35 lines · 78 tokens per session scan A a9fd47607ed5
feature-architect is an agent published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 516 once invoked, about $0.0004 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.