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 ArcBlock/agent-skills --skill design-reviewgit clone --depth 1 https://github.com/ArcBlock/agent-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/arcblock/agent-skills/design-review)<a href="https://agentmods.dev/skills/arcblock/agent-skills/design-review"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/design-review/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/arcblock/agent-skills/design-review"><img src="https://agentmods.dev/badge/skills/arcblock/agent-skills/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 486 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.00053 | $0.07568 |
| Opus 5 | $0.00026 | $0.03784 |
| Sonnet 5 | $0.00011 | $0.01514 |
| Haiku 4.5 | $0.00005 | $0.00757 |
Grade A, and why
design-review 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 9d 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review — Iterative Clean-Context Review Loop
Repo profile — read
.claude/repo-profile.mdfirst. This skill is repo-agnostic; arc is the reference implementation. Where it references repo identity or paths, read the profile (repo_slugetc.). Arc's own provenance for any lessons is not inlined here (fuller case narratives, where they exist, are under.claude/case-law/).
Automate design document review using clean-context subagents. Each round gets a fresh perspective — no inherited bias from the current conversation.
Usage
/agentloop:design-review <path> [--target <score>] [--max-rounds <n>]
<path>— Path to a design document file, or a directory containingdesign.md+tasks.md--target <score>— Target completeness score (default: 95)--max-rounds <n>— Maximum review iterations (default: 5)
Examples
/agentloop:design-review planning/provider-architecture-rethink/
/agentloop:design-review intent/my-feature/INTENT.md --target 90
/agentloop:design-review planning/my-plan/ --target 95 --max-rounds 3
Issue-driven plans (no planning/ file — issue is the source of truth)
When the plan originated in a GitHub issue (the human confirmed it in the
comments), do NOT commit a planning/ doc — those
tracker docs rot and become the next audit's deletion. The issue is the source
of truth; the file is throwaway:
- Render an ephemeral working copy of the confirmed plan (a
design.md/tasks.md) into a scratch / gitignored dir (e.g. the session scratchpad) from the issue. Run/agentloop:design-review <scratch-dir>on it. The rounds are disposable iterations on a disposable file. - When it hits the target score, post the final optimized plan back to the issue as a comment — that comment is the durable artifact.
- Add a brief round summary: how many rounds, and the key improvement each
round made. Then discard the scratch file. Nothing lands in
planning/.
Autonomous escalation — ask via an issue comment, never block in-session.
In the issue-native flow nobody is babysitting the session, so an escalation
that would normally call AskUserQuestion and wait must instead be posted as
a comment on the source issue and the run paused there. If the review loop hits
an unrecoverable point — a genuine design fork, an AskUserQuestion-worthy
ambiguity, a needed architecture change, or an AFS-principle conflict (see the
ESCALATION list under "Step 5: Fix Issues") — do not sit waiting for an
inline answer. Post a clear, self-contained question comment on the issue (state
the options, your recommendation, and what's blocked), then stop that work item.
The human answers asynchronously on the issue; the next sweep picks it up. Only
fall back to inline AskUserQuestion when a human is demonstrably present and
interacting in this session.
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.
- 9d ago First seen · 504 lines · 53 tokens per session scan A a730711fb9ed
design-review is a skill published in the GitHub repository ArcBlock/agent-skills (5 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 7,568 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…