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 skills add tikalk/adlc-team-skills --skill factory-architectgit clone --depth 1 https://github.com/tikalk/adlc-team-skillsWrote 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/skills/tikalk/adlc-team-skills/factory-architect)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/factory-architect"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/factory-architect/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.
<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/factory-architect"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/factory-architect.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00909 |
| Opus 5.5 | $0.00012 | $0.00364 |
| Sonnet 5.5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
factory-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 15d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
factory-architect
What this skill does
factory-architect orchestrates the architecture-decisions lifecycle. It coordinates individual architecture-related skills (architect-init, architect-specify, architect-clarify, architect-implement, architect-analyze) to maintain a consistent AD.md at the project root.
It operates as a Kind-A DAG orchestrator in alignment with the shared executor engine contract in factory-mission/references/executor.md.
When to use
- You want to bootstrap, refine, or analyze a project's system-level design and decisions (ADRs) end-to-end.
- You want to verify that architectural viewpoints conform to the Rozanski & Woods methodology.
When NOT to use:
- For product-requirements definition (use
factory-productinstead). - For feature-level software execution (use
factory-missioninstead).
Lifecycle DAG & Step Resolution
factory-architect implements a fixed named-skill DAG (fixed step resolution):
Greenfield Route (default on empty project)
specify(generatephase) -> Invokearchitect-specifyto collaboratively capture ADR drafts in.adlc/drafts/adr/.clarify⭐ (clarifyphase) -> Invokearchitect-clarifyto run interactive quality checks and mark ADRs Accepted (human sign-off gate).implement(buildphase) -> Invokearchitect-implementto compile accepted ADRs intoAD.md(by sub-systems) and promote them todocs/adlc/memory/adr/.analyze(analyzephase) -> Invokearchitect-analyzeto verify AD/ADR consistency and output a severity-ranked report.
Brownfield Route (default if code exists but no ADRs)
init(generatephase) -> Invokearchitect-initto reverse-engineer draft ADRs from the existing architecture.clarify⭐ →implement→analyze(same as Greenfield).
Refresh Route (default if AD.md and memory ADRs already exist)
analyze(analyzephase) -> Run architect-analyze first to detect drift.clarify⭐ →implement→analyze(drift-correction cycle).
What ships with it
1 file 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.
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.
- 15d ago Changed b4257967efdd
- 25d ago First seen · 61 lines · 29 tokens per session scan A 743824e67cad
factory-architect is a skill published in the GitHub repository tikalk/adlc-team-skills (141 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 909 once invoked, about $0.0001 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-09-21.
Other skills, from other repositories
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
decision-records
Use when a hard-to-reverse choice (database, framework, vendor, auth model) must be frozen as an immutable numbered ADR — the context that forced it, the options weighed, the decision, consequences both ways — or superseded without erasing history. NOT a meeting recap (that is meeting-notes), NOT standing project…
prompt-engineering
Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…
respect-the-oracle
Use when working against a test suite, spec, or graded harness you do not own - especially inside an automated loop scored on how many tests pass - and tempted to change the tests, weaken assertions, hardcode expected outputs, special-case inputs, or overfit the visible examples to turn things green.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.