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-report)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-code-report"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-code-report/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-report"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-code-report.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.00163 | $0.01813 |
| Opus 5.5 | $0.00065 | $0.00725 |
| Sonnet 5.5 | $0.00033 | $0.00363 |
| Haiku 4.5 | $0.00016 | $0.00181 |
Grade A, and why
arn-code-report 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Code Report
Report an Arness Code workflow issue by running a diagnostic and filing a GitHub issue on the Arness plugin repository. The arn-code-doctor agent analyzes Arness Code configuration and behavior — it never reads project source code or business logic. Supports cross-plugin smart routing — detects if the issue belongs to Spark or Infra and suggests the right report skill.
Workflow
Step 0: Smart Routing
Before gathering details, check if the issue might belong to another plugin:
- Read
## Arnessfrom the project's CLAUDE.md. - If the user has already described the issue (e.g., in their initial message), scan for keyword signals:
- Spark keywords: "discover", "prototype", "greenfield", "stress test", "naming", "brainstorming", "feature extract", "visual sketch", "use cases", "scaffold", "spike"
- Infra keywords: "deploy", "Dockerfile", "container", "IaC", "terraform", "pipeline", "CI/CD", "environment", "secrets", "monitor", "infrastructure", "verify", "cleanup"
- If Spark signals detected and Spark fields exist in
## Arness: suggest "This sounds like an Arness Spark issue. Run/arn-spark-reportinstead, or confirm this is a Code issue." - If Infra signals detected and Infra fields exist in
## Arness: suggest "This sounds like an Arness Infra issue. Run/arn-infra-reportinstead, or confirm this is a Code issue." - If no signals or user confirms it's a Code issue: proceed to Step 1.
Step 1: Explain the Process
Inform the user:
"I'll help you report a Arness workflow issue. Here's how this works:
- You describe what happened — which skill you used and what went wrong
- I'll run a diagnostic that checks Arness's configuration and expected behavior (I won't read your project code)
- You'll review the issue report before it's submitted
- The issue gets filed on the Arness plugin repository for the maintainers
Your project code and business logic are never included in the report."
Step 2: Gather User Description
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 · 145 lines · 163 tokens per session scan A e068a66d40e6
arn-code-report is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 163 tokens to every session and 1,813 once invoked, about $0.0007 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
pulumi-debug-failed-operation
Debug a Pulumi update or preview that failed: read the failure Pulumi already recorded, find what caused it, and fix it. Load this skill when the user asks to debug, diagnose, or fix a failed update or preview, or points at a failing pulumi up or pulumi preview. Don't load it for authoring new infrastructure…
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
bug-fixer
A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.