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 architect-initgit 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/architect-init)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/architect-init"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-init/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-init"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 225 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.
- medium Excessive Agency · line 228 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.00032 | $0.06759 |
| Opus 5 | $0.00016 | $0.03379 |
| Sonnet 5 | $0.00006 | $0.01352 |
| Haiku 4.5 | $0.00003 | $0.00676 |
Grade A, and why
architect-init 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 10d 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 — 749 lines — stays where its author put it; the contents beside it link to each section on GitHub.
architect-init
What this skill does
Reverse-engineer architecture from an existing codebase (brownfield) to create Architecture Decision Records (ADRs) documenting discovered decisions, then validate the findings by running /architect-clarify manually.
You act as an Architecture Archaeologist uncovering implicit architectural decisions from code by scanning the codebase for technology choices and patterns, inferring architectural decisions from code structure, documenting discovered patterns as ADRs, and identifying gaps where decisions are unclear.
Output:
- ADRs documenting inferred architectural decisions in
{REPO_ROOT}/.adlc/drafts/adr/ADR-{NNN}.md(individual file format) - Auto-generated index at
{REPO_ROOT}/.adlc/drafts/adr/adr.md - Validate Findings: Run
/architect-clarifyto validate discovered decisions
Key Difference from /architect-specify:
/architect-init(this skill) = Discovers what's already implemented in code/architect-specify= Explores new possibilities for greenfield projects
This skill focuses on current state analysis - what IS, not what SHOULD BE.
When to use
- Brownfield projects: Existing code without architecture docs
- Legacy modernization: Understanding current state before changes
- Team onboarding: Quickly documenting implicit decisions
- Technical debt assessment: Identifying undocumented patterns
When NOT to use
- Greenfield projects: Use
/architect-specifyfor new projects - Architecture exists: If
AD.mdexists, use/architect-clarifyto refine - Feature-level: Feature architecture (if Spec Kit extension is also installed)
Process
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Examples of User Input:
"Django monolith with PostgreSQL, React frontend, AWS deployment""Node.js microservices with MongoDB and RabbitMQ""Legacy Java application, focus on understanding data layer"- Empty input: Scan entire codebase and infer architecture
What ships with it
26 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
- templates/AD-template.md 13 KB
- templates/adr-template.md 4.5 KB
- templates/perspectives/accessibility.md 2.3 KB
- templates/perspectives/availability.md 2.9 KB
- templates/perspectives/development-resource.md 2.6 KB
- templates/perspectives/evolution.md 2.7 KB
- templates/perspectives/internationalization.md 2.3 KB
- templates/perspectives/location.md 2.4 KB
- templates/perspectives/performance.md 2.4 KB
- templates/perspectives/regulation.md 2.4 KB
- templates/perspectives/security.md 2.5 KB
- templates/perspectives/usability.md 2.5 KB
- templates/views/concurrency.md 2.2 KB
- templates/views/context.md 3.9 KB
- templates/views/deployment.md 2.9 KB
- templates/views/development.md 5.0 KB
- templates/views/functional.md 3.4 KB
- templates/views/information.md 2.8 KB
- templates/views/operational.md 2.2 KB
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.
- 10d ago First seen · 749 lines · 32 tokens per session scan A c5eb5769ed6a
architect-init is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 6,759 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
cognitive-doc-design
Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.