Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tikalk/adlc-team-skillsnpx agentmods add skills/tikalk/adlc-team-skills/architect-implementWrote 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/architect-implement)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/architect-implement"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-implement/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/architect-implement"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 474 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00023 | $0.12525 |
| Opus 5.5 | $0.00009 | $0.05010 |
| Sonnet 5.5 | $0.00005 | $0.02505 |
| Haiku 4.5 | $0.00002 | $0.01252 |
Grade A, and why
architect-implement 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 — 1,277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
architect-implement
What this skill does
Generate a full Architecture Description (AD.md) from Architecture Decision Records (ADRs) using a multi-agent DAG orchestration approach:
- Plan Agent: Analyze ADRs, detect sub-systems, generate a customized DAG, and get user approval.
- Execute Agent: Generate architecture views per sub-system following the DAG, with dependency context passing.
- Summarize Agent: Aggregate all views, resolve cross-subsystem conflicts, and generate a unified AD.md.
Key Insight: ADRs capture why decisions were made; the Architecture Description captures what the system looks like as a result of those decisions.
When to use
- After
/architect-specifyor/architect-clarify: Generate AD from discussed and accepted ADRs. - After
/architect-init: Document brownfield architecture. - ADR Updates: Regenerate AD.md after new decisions.
- Documentation Sprint: Create comprehensive architecture docs.
When NOT to use
- No ADRs exist: Use
/architect-specifyor/architect-initfirst. - Feature-level: Feature AD is generated during the feature's plan phase, not by this skill.
- Minor updates: Use direct editing for small changes.
Process
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Examples of User Input:
"Focus on deployment and operational views - we need infrastructure docs""Generate all views with emphasis on security perspective""Update existing AD.md with new ADRs from recent decisions"- Empty input: Generate complete Architecture Description from all ADRs
Flags
-
--views VIEWS: Architecture views to generatecore(default): Context, Functional, Information, Development, Deployment (5 core views)all: All 7 views including Concurrency and Operational- Custom: comma-separated (e.g.,
concurrency,operational) - always includes core views
-
--sequential(default): Execute views sequentially for maximum quality- Recommended: Allows checkpoint after Functional view
-
--parallel: Allow parallel execution where dependency chains permit- Warning: May reduce cross-view consistency - use only when time-constrained
What ships with it
7 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.
- scripts/bash/ascii-generator.sh 18 KB runs code
- scripts/bash/common.sh 3.1 KB runs code
- scripts/bash/mermaid-generator.sh 8.9 KB runs code
- scripts/bash/setup-architect.sh 54 KB runs code
- scripts/powershell/ASCII-Generator.ps1 18 KB runs code
- scripts/powershell/Mermaid-Generator.ps1 8.9 KB runs code
- scripts/powershell/setup-architect.ps1 49 KB runs code
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 Changed 8154b7821f1e
- 25d ago Changed abd12a54afc2
- 26d ago Changed e599844ae488
- 1mo ago Changed · -18 tokens per session d5d36cccbe66
- 1mo ago Changed · +3 lines bde29b05771b
- 1mo ago First seen · 1,274 lines · 41 tokens per session scan A db28ebffb1a2
architect-implement is a skill published in the GitHub repository tikalk/adlc-team-skills (143 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 12,525 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-08-30.
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.