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 agentmods add skills/appsvortex/arness/arn-code-sketchnpx skills add AppsVortex/arness --skill arn-code-sketchgit clone --depth 1 https://github.com/AppsVortex/arnessWhat 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 | $0.00163 | $0.03801 |
| Opus 5 | $0.00081 | $0.01901 |
| Sonnet 5 | $0.00033 | $0.00760 |
| Haiku 4.5 | $0.00016 | $0.00380 |
Grade A, and why
arn-code-sketch 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 2d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Sketch
Create a working interface preview of a feature using the project's actual framework, conventions, and styling system. The sketch renders the new feature in context -- showing it within the real application where it will live, not in isolation. This lets the user see and interact with a preview before committing to the full implementation pipeline.
Sketches are real code: runnable artifacts written with the project's conventions, served from a dedicated arness-sketches/ namespace. They can be iterated on via feedback, promoted into the real codebase, or cleaned up when no longer needed.
This is a conversational skill. It runs in normal conversation (NOT plan mode).
Prerequisites
-
Arness must be configured. Read the project's CLAUDE.md and check for a
## Arnesssection. If missing, inform the user: "Arness is not configured for this project yet. Run/arn-implementingto get started — it will set everything up automatically." Do not proceed without it. -
Sketch strategy must exist. Read
ui-patterns.mdfrom the project's code patterns directory (the path under Code patterns: in the## Arnessconfig). Look for a## Sketch Strategysection. If absent, halt with:"No sketch strategy found. Run
/arn-implementingto get started — pattern documentation will be generated on first use, including the sketch strategy if your project has a UI framework."Do not proceed without a sketch strategy.
Pipeline Position
Entry points:
- Direct: user says "sketch this" / "preview this"
- From feature-spec: proactively offered after initial proposal when UI is involved
- From feature-spec-teams: proactively offered after debate converges when UI is involved
- From swift: after swift assessment, offered for interface changes above threshold
arn-code-sketch (this skill)
=========================
For interface preview before implementation
Input: Feature description (from spec, swift, or direct)
|
v
Load: Sketch strategy + paradigm reference from pattern docs
|
v
Assess: Should this be sketched? (threshold rules)
|
+--- Below threshold --> "This change is small enough to implement
| directly. Proceed with /arn-code-swift or
| /arn-code-feature-spec instead."
|
+--- Above threshold --> Continue
|
v
Create: arness-sketches/[feature-name]/ artifact namespace
|
v
Build: Spawn arn-code-sketch-builder agent
|
v
Present: Show preview instructions, iterate on feedback
|
v
Finish: Promote to real codebase OR clean up
What ships with it
6 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.
- 2d ago First seen · 298 lines · 163 tokens per session scan A 0305c5dd32da
arn-code-sketch is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 163 tokens to every session and 3,801 once invoked, about $0.0008 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
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agentmail
Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.
aria
Designs the data model, API contracts, and structural foundation of the system.
luna
Reviews code for objective correctness, security, and reliability.
max
Cleans up and improves existing code without changing behavior.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.