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-clarifygit 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-clarify)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/architect-clarify"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-clarify/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-clarify"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/architect-clarify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 59 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.
- high Memory Poisoning · line 218 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.
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.00028 | $0.04506 |
| Opus 5.5 | $0.00011 | $0.01802 |
| Sonnet 5.5 | $0.00006 | $0.00901 |
| Haiku 4.5 | $0.00003 | $0.00451 |
Grade A, and why
architect-clarify 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 — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.
architect-clarify
What this skill does
Identify underspecified areas in existing ADRs and refine them through targeted clarification questions. Ensure ADRs are complete, consistent, and ready for architecture generation.
You act as an Architecture Reviewer ensuring ADR quality by:
- Validating ADR completeness against MADR standards
- Identifying gaps in consequences or alternatives
- Detecting conflicts between ADRs or with constitution
- Refining decisions through targeted clarification
When to use
Use this skill:
- After
/architect-init: Refine initial ADRs before architecture generation - ADR Review: Validate ADRs before major milestones
- New Team Member: Ensure ADRs make sense to fresh eyes
- Conflict Resolution: Resolve identified inconsistencies
Do not use this skill when:
- No ADRs exist: Use
/architect-initfirst to create ADRs - Brownfield projects: Use
/architect-initto reverse-engineer ADRs from code
Process
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Examples of User Input:
"Focus on data architecture decisions - we're reconsidering database choice""Security ADRs need more detail for compliance review""ADR-003 consequences seem incomplete"- Empty input: Review all ADRs for completeness
Goal
Identify underspecified areas in existing ADRs and refine them through targeted clarification questions. Ensure ADRs are complete, consistent, and ready for architecture generation.
ADR Quality Checklist
Each ADR should have:
- Clear context explaining the problem/opportunity
- Explicit decision statement
- Positive AND negative consequences
- Common Alternatives documented (neutral trade-offs, not "Rejected because")
- Risks identified with mitigation strategies
- Status is accurate (Proposed/Accepted/Deprecated/Superseded/Discovered)
- No conflicts with other ADRs
- Alignment with constitution principles
- No fabricated rejection rationale for reverse-engineered ADRs
What ships with it
10 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.6 KB runs code
- scripts/bash/mermaid-generator.sh 8.9 KB runs code
- scripts/bash/mermaid-lint.sh 19 KB runs code
- scripts/bash/setup-architect.sh 63 KB runs code
- scripts/powershell/ascii-generator.ps1 18 KB runs code
- scripts/powershell/common.ps1 3.5 KB runs code
- scripts/powershell/mermaid-generator.ps1 8.9 KB runs code
- scripts/powershell/mermaid-lint.ps1 18 KB runs code
- scripts/powershell/setup-architect.ps1 51 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 984bcdd8bcff
- 25d ago Changed c5457af3231d
- 1mo ago Changed · +20 lines 426530e5b37c
- 1mo ago Changed · -11 tokens per session 5a89a5bda4cb
- 1mo ago First seen · 555 lines · 39 tokens per session scan A 17bf69fbaf42
architect-clarify is a skill published in the GitHub repository tikalk/adlc-team-skills (143 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 4,506 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.