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-specifygit 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-specify)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/architect-specify"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-specify/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-specify"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Memory Poisoning · line 601 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Excessive Agency · line 220 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 223 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.00034 | $0.05559 |
| Opus 5 | $0.00017 | $0.02780 |
| Sonnet 5 | $0.00007 | $0.01112 |
| Haiku 4.5 | $0.00003 | $0.00556 |
Grade A, and why
architect-specify 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 — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
architect-specify
What this skill does
Transform a PRD (Product Requirements Document) or high-level system description into well-documented Architecture Decision Records (ADRs) through interactive exploration and trade-off analysis.
Key Insight: Unlike direct architecture generation, this skill prioritizes discussion and exploration before committing to formal documentation. The goal is to surface trade-offs, validate assumptions, and make informed decisions collaboratively.
You act as a Solutions Architect facilitating an architectural discovery session. Your role involves:
- Exploring possible solutions and their trade-offs
- Asking clarifying questions to surface hidden requirements
- Proposing options with clear consequences
- Documenting decisions in MADR format once consensus is reached
When to use
- New projects: Starting system architecture from scratch
- Major changes: Significant architectural shifts requiring new decisions
- Documentation: Capturing verbal decisions as formal ADRs
- Team onboarding: Walking through architectural rationale with new members
When NOT to use:
- Brownfield projects: Use
/architect-initinstead to reverse-engineer from code - Minor updates: Use
/architect-clarifyfor ADR refinements - 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:
"B2B SaaS platform for supply chain management with real-time inventory tracking""Mobile-first e-commerce app with offline support and social features""Legacy system modernization: migrate from monolith to microservices""IoT platform for smart home devices with edge computing requirements"
When users provide PRD context like this, use it to drive the architectural exploration conversation.
Flags
--views VIEWS: Architecture views to include in final AD.mdcore(default): Context, Functional, Information, Development, Deploymentall: All 7 views including Concurrency and Operational- Custom: comma-separated (e.g.,
concurrency,operational)
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 · 646 lines · 34 tokens per session scan A 4e6ed8120f98
architect-specify is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 5,559 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…