What is arch-lens-scenarios?

An architecture-diagram tool focused on end-to-end user journeys and how software components cooperate. It selects a small set of representative scenarios and shows their component touchpoints in sequence.

Use it to document key user scenarios, trace requests through components, and validate end-to-end architecture.

It helps reveal whether the parts of a system work together across a complete user flow, rather than only describing each part separately.

arch-lens-scenarios — Skill for Claude Code by TalonT-Org

Install

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.

Any agent

npx skills add TalonT-Org/AutoSkillit --skill arch-lens-scenarios

Clone the repo

git clone --depth 1 https://github.com/TalonT-Org/AutoSkillit

Made for: Claude Code.

Or install autoskillit, the plugin that ships this one along with the rest of its 121 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/talont-org/autoskillit/arch-lens-scenarios/github.svg)](https://agentmods.dev/skills/talont-org/autoskillit/arch-lens-scenarios)

Your own site

<a href="https://agentmods.dev/skills/talont-org/autoskillit/arch-lens-scenarios"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/arch-lens-scenarios/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/talont-org/autoskillit/arch-lens-scenarios"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/arch-lens-scenarios.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,301 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.02301
Opus 5	$0.00016	$0.01151
Sonnet 5	$0.00007	$0.00460
Haiku 4.5	$0.00003	$0.00230

Measured 11d ago against content hash 24474d80e3d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

arch-lens-scenarios 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 11d 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.

src/autoskillit/skills_extended/arch-lens-scenarios/SKILL.md · 298 lines

How it starts

The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scenarios Architecture Lens

Cognitive Mode: Validation (+1 Validator) Primary Question: "Do the components work together?" Focus: End-to-End User Journeys, Component Cooperation, Scenario Validation

When to Use

Need to validate component cooperation
Documenting key user scenarios
Analyzing end-to-end flows through architecture
User invokes /autoskillit:arch-lens-scenarios or /autoskillit:make-arch-diag scenarios

Critical Constraints

NEVER:

Modify any source code files
Show internal component details
Include all possible scenarios (pick key ones)
Run subagents in the background (run_in_background: true is prohibited)

ALWAYS:

Focus on END-TO-END journeys
Show component touchpoints in sequence
Select 3-5 representative scenarios
Validate components work together
BEFORE creating any diagram, LOAD the /autoskillit:mermaid skill using the Skill tool - this is MANDATORY
If the Skill tool cannot be used (disable-model-invocation) or refuses this invocation, do NOT proceed with diagram creation. Abort this step and omit the diagram from output.
After writing the diagram file, emit the absolute path as a structured output token as your final output. Resolve the relative temp/arch-lens-scenarios/... save path to absolute by prepending the full CWD:
```
diagram_path = /absolute/cwd/temp/arch-lens-scenarios/{filename}.md
```
This token is MANDATORY — the pipeline cannot proceed without it.

Arguments

/autoskillit:arch-lens-scenarios [context_path]

context_path (optional) — Absolute path to a PR context file containing new files (★-prefixed) and modified files (●-prefixed) from the PR diff. When provided, read this file before beginning analysis and focus the diagram on the architectural areas affected by these specific files. When absent, explore the full CWD.

Analysis Workflow

Step 0: Read PR context (when provided)

If a context_path positional argument is present:

Read the file at context_path
Extract: new files list (★-prefixed), modified files list (●-prefixed)
Focus Step 1 exploration on the modules/components these files belong to
Apply ★ prefix on diagram nodes representing new files/components
Apply ● prefix on diagram nodes representing modified files/components

Read the full file on GitHub · 298 lines

Changes

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.

11d ago First seen · 298 lines · 33 tokens per session scan A 24474d80e3d5

Subscribe to this mod's changes

arch-lens-scenarios is a skill published in the GitHub repository TalonT-Org/AutoSkillit (5 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,301 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-31.

Design and UX Planning arch-lens

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

arch-lens-scenarios