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 skills add AppsVortex/arness --skill arn-code-execute-taskgit clone --depth 1 https://github.com/AppsVortex/arnessWrote 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-execute-task)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-code-execute-task"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-code-execute-task/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-execute-task"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-code-execute-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.02839 |
| Opus 5.5 | $0.00034 | $0.01136 |
| Sonnet 5.5 | $0.00017 | $0.00568 |
| Haiku 4.5 | $0.00009 | $0.00284 |
Grade A, and why
arn-code-execute-task 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Execute Task
Execute a single task from the task list by spawning a arn-code-task-executor agent. Optionally run a arn-code-task-reviewer to validate the implementation before marking the task complete.
Pipeline position (this is an alternative entry point, not in the main pipeline):
arn-code-taskify -> arn-code-execute-task (single task) -> [optional] arn-code-review-implementation
Use cases:
- Re-running a failed task after manual intervention
- Testing a single phase independently
- Implementing one task without the full pipeline
- Retrying a task that was escalated during arn-code-execute-plan
Prerequisites
If no ## Arness section exists in the project's CLAUDE.md, inform the user: "Arness is not configured for this project yet. Run /arn-implementing to get started — it will set everything up automatically." Do not proceed without it. Task list must exist (run /arn-code-taskify first).
Workflow
Step 1: Load Configuration
-
Read the project's CLAUDE.md and extract the
## Arnesssection to find:- Plans directory -- base path where project plans are saved
- Code patterns -- path to the directory containing stored pattern documentation
- Template path -- path to the report template set (JSON templates)
- Template version -- plugin version the templates were copied from (if present)
- Template updates -- user preference:
ask,auto, ormanual(if present) - Specs directory -- path to the directory containing specification files (if present)
Template version check: If
Template versionandTemplate updatesfields are present, run the template version check procedure documented in arn-code-save-plan Step 1 (Template Version Check) before proceeding. If## Arnessdoes not contain these fields, treat as legacy and skip.
Step 2: Identify the Task
- If user provided a task ID or number: verify it exists in TaskList
- If user provided a description: search TaskList for a matching task
- If no task specified: show all available tasks (pending, unblocked) and ask user to choose
- Show the selected task: ID, description, status, dependencies
- If task is blocked: warn user that dependencies haven't completed, ask if they want to proceed anyway
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 · 201 lines · 86 tokens per session scan A 15017fef89a3
arn-code-execute-task is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 2,839 once invoked, about $0.0003 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
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).