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-sparkWrote 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-spark-report)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-spark-report"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-spark-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-spark-report"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-spark-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.00131 | $0.01760 |
| Opus 5.5 | $0.00052 | $0.00704 |
| Sonnet 5.5 | $0.00026 | $0.00352 |
| Haiku 4.5 | $0.00013 | $0.00176 |
Grade A, and why
arn-spark-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 today.
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 Spark Report
Report an Arness Spark workflow issue by running a diagnostic and filing a GitHub issue on the Arness plugin repository. The arn-spark-doctor agent analyzes Spark configuration and behavior — it never reads project source code or business logic.
Workflow
Step 0: Smart Routing
Before proceeding, check whether the user's issue actually belongs to a different Arness plugin:
- Read the
## Arnesssection from the project's CLAUDE.md (if it exists). - Check the user's description for keyword signals:
- Code keywords: "plan", "spec", "execute", "taskify", "swift", "standard", "batch", "ship", "PR", "review-pr", "assess", "catch-up", "document-project", "save-plan"
- Infra keywords: "deploy", "Dockerfile", "container", "IaC", "terraform", "pipeline", "CI/CD", "environment", "secrets", "monitor", "infrastructure"
- If Code signals detected: "This sounds like an Arness Code issue. Run
/arn-code-reportinstead." - If Infra signals detected: "This sounds like an Arness Infra issue. Run
/arn-infra-reportinstead." - If the user confirms it is actually a Spark issue, proceed.
Step 1: Explain the Process
Inform the user:
"I'll help you report an Arness Spark 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 Spark'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
Ask the user to describe the issue (free-form text, not AskUserQuestion — this is open-ended):
"What happened? Which Arness Spark skill were you using and what went wrong?"
Let the user type a free-form description. This becomes the user_description for the diagnostic.
Step 3: Check Prerequisites
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.
- today First seen · 145 lines · 131 tokens per session scan A 460035cb6210
arn-spark-report is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 1,760 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-10-25.
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.
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.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
windows-compat
Audit and harden this Rust repo (code-graph-mcp) for Windows correctness: path-spelling drift between producers, the 32,767-char command-line cap, index-key mismatches, and path predicates that assume one ecosystem's layout. Use whenever touching code that builds, compares, prints, or stores a filesystem path; that…
chaos
Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…