Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AppsVortex/arness/plugin install arn-codeWrote 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/appsvortex/arness/arn-code-assess)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-code-assess"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-code-assess/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/appsvortex/arness/arn-code-assess"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-code-assess.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.00133 | $0.03867 |
| Opus 5.5 | $0.00053 | $0.01547 |
| Sonnet 5.5 | $0.00027 | $0.00773 |
| Haiku 4.5 | $0.00013 | $0.00387 |
Grade A, and why
arn-code-assess 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 1mo 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Assess
Run a comprehensive technical assessment of the codebase against stored patterns, let the user prioritize findings, then orchestrate the full Arness pipeline (spec → plan → execute → test → ship) for multiple improvements in a single session.
This skill is a sequencer and decision-gate handler, like arn-planning. It MUST NOT duplicate sub-skill or agent logic. All pipeline work is done by the invoked skills and agents. This skill handles: scope selection, assessment orchestration, finding prioritization, multi-spec pipeline management, and progress display.
Prerequisites
Check for a ## Arness section in the project's CLAUDE.md. If missing, inform the user: "Arness is not configured for this project yet. Run /arn-assessing to get started — it will set everything up automatically." Do not proceed without it.
Additionally, verify that pattern files exist at the configured code-patterns path. At minimum, these must exist:
code-patterns.mdtesting-patterns.mdarchitecture.md
If any required pattern file is missing, inform the user: "Pattern documentation is incomplete. Run /arn-assessing which will generate pattern docs on first use."
Decision Gates
The skill pauses at exactly 7 gates. Steps marked (auto) flow without stopping.
| Gate | When | Question | Options |
|---|---|---|---|
| G1 | Entry | "What would you like to assess?" | Entire codebase / Specific area |
| G2 | After assessment | "Ready to prioritize?" | Prioritize / Investigate further |
| G3 | After prioritization | "How should improvements be organized?" | Bundle all / Separate specs / Arness suggests groupings |
| G4 | After all plans generated | "Plans ready. Proceed?" | Approve all / Revise specific plan / Remove a spec |
| G5 | Before each subsequent spec execution | "Conflict detected" (conditional) | Re-plan / Proceed / Skip |
| G6 | After test results | "Tests [pass/fail]. Proceed?" | Ship / Fix and re-test / Abort |
| G7 | Final | "Ship it?" | Commit, push & PR / Just commit / Not yet |
What ships with it
2 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.
- 1mo ago First seen · 391 lines · 133 tokens per session scan A 7e1bb4e7c83f
arn-code-assess is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 133 tokens to every session and 3,867 once invoked, about $0.0005 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
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
shipyard-executing-plans
Executes a written implementation plan with agents. Use when a written plan is ready to execute, in the current session or a separate one. Also use when the user says "build this", "implement this", "execute the plan", or "run the plan", or when a loaded plan file has independent tasks suitable for agent dispatch.