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-assessing)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-assessing"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-assessing/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-assessing"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-assessing.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.00132 | $0.00804 |
| Opus 5.5 | $0.00053 | $0.00322 |
| Sonnet 5.5 | $0.00026 | $0.00161 |
| Haiku 4.5 | $0.00013 | $0.00080 |
Grade A, and why
arn-assessing 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Assessing
Comprehensive technical assessment of the codebase against stored patterns, followed by prioritized improvement identification. This is a first-citizen entry point that wraps arn-code-assess with a pre-flight check and provides chaining context to arn-implementing.
This skill is a medium orchestration wrapper. It MUST NOT duplicate arn-code-assess logic. All assessment work is done by the invoked skill (which has its own 7 internal gates). Arness-assessing handles: prerequisite checks, pre-flight validation, invoking the assess skill, and offering the chain exit.
Step 0: Ensure Configuration
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/step-0-fast-path.md and follow its instructions. This guarantees a user profile exists and ## Arness is configured with Arness Code fields before proceeding.
After Step 0 completes, extract the following from ## Arness:
- Code patterns — path to the directory containing stored pattern documentation
Workflow
Step 1: Pre-flight Check
Verify that pattern documentation exists at the configured Code patterns path:
<code-patterns-dir>/code-patterns.md<code-patterns-dir>/testing-patterns.md<code-patterns-dir>/architecture.md
If any are missing: inform the user: "Pattern documentation is incomplete. The assessment needs stored patterns to compare against. Run /arn-planning first — it will generate pattern docs on first use." Do not proceed.
If all exist: inform the user briefly: "Pattern documentation found. Starting assessment..."
Step 2: Invoke Assess
Show progress:
Assessing: PRE-FLIGHT -> ASSESSMENT (scope -> analyze -> prioritize -> spec -> plan -> execute -> ship -> update-patterns)
^^^^^^^^^^
Invoke the assess skill:
Skill: arn-code:arn-code-assess
The assess skill has its own 7 internal decision gates (scope selection, improvement selection, spec review, execution mode, etc.) and manages its own complete pipeline internally. Wait for it to complete.
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 · 83 lines · 132 tokens per session scan A 107af5bf9e7b
arn-assessing is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 132 tokens to every session and 804 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
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Routes to the triagehelper.py helper for identity checks, thread snapshotting, isolated-worktree fixes, and publish/reply/resolve mechanics; you classify the finding and apply a justified fix. --dry-run is fully read-only (investigation and a printed…
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
genshijin-review
A compact pull-request review format that writes one actionable finding per line in Japanese or English.
pr-review
Use when the user wants to deeply review a pull/merge request or a local diff — "review this PR", "grill the MR", "stress-test this diff", "deep-dive code review", "code review before merge", or when they name a PR/MR URL, number, branch, commit range (A..B/A...B), tag or SHA. Works on GitHub (gh), GitLab (glab), or a…