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 utsavanand/uv-suite --skill uvs-architectgit clone --depth 1 https://github.com/utsavanand/uv-suiteWrote 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/utsavanand/uv-suite/uvs-architect)<a href="https://agentmods.dev/skills/utsavanand/uv-suite/uvs-architect"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-architect/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/utsavanand/uv-suite/uvs-architect"><img src="https://agentmods.dev/badge/skills/utsavanand/uv-suite/uvs-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01605 |
| Opus 5.5 | $0.00014 | $0.00642 |
| Sonnet 5.5 | $0.00007 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
uvs-architect 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 2mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input
$ARGUMENTS
Session output directory
Write architecture artifacts under this directory (scoped to the current session):
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-session.sh
Step 0 — REQUIRE a curated spec (HARD GATE — do this before anything else)
Architecture is designed from a spec. Do not design without one. Do not proceed past this step until a real spec is in hand. A "curated spec" is a spec document with a problem statement, requirements, and success criteria — not a one-line description.
Resolve the spec in this exact order:
-
$ARGUMENTSnames a spec file →Readit in full. Proceed. -
A spec exists in the CURRENT session (see "Available specs" below) →
Readthe newest one in full. Proceed. -
Only PRIOR-session specs exist → ask with
AskUserQuestionwhich to use (list each with its session + date, default newest).Readit. Proceed. -
No spec anywhere (and
$ARGUMENTSis empty or just a vague phrase) → STOP. Do NOT architect. Ask withAskUserQuestion, offering:- Run
/uvs-specfirst (recommended — architecture needs a curated spec), or - Describe the problem now → if they choose this, draft a brief spec inline (problem · requirements · success criteria), confirm it with the user, and only then continue to design from it.
Never invent requirements, and never design from a single sentence — if that's all you have, you are in case 4.
- Run
If you cannot satisfy one of cases 1–3 or complete case 4's confirmation, end here with a one-line explanation. Designing without a spec is a failure, not a fallback.
Project context
!cat CLAUDE.md 2>/dev/null || echo "No CLAUDE.md found"
Available specs (current session first, then prior, then legacy)
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-collect.sh 'specs/*.md' || echo "No specs found"
Prior analysis
Codebase map (current session first)
!"${CLAUDE_PROJECT_DIR:-.}"/.claude/hooks/uv-out-collect.sh 'map-codebase.md' || echo "No codebase map"
What ships with it
4 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.
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.
- 2mo ago First seen · 144 lines · 34 tokens per session scan A 33cd7ba34213
uvs-architect is a skill published in the GitHub repository utsavanand/uv-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 1,605 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…