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 agentmods add skills/appsvortex/arness/arn-code-document-projectnpx skills add AppsVortex/arness --skill arn-code-document-projectgit clone --depth 1 https://github.com/AppsVortex/arnessWhat 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 | $0.00101 | $0.01379 |
| Opus 5 | $0.00051 | $0.00690 |
| Sonnet 5 | $0.00020 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
arn-code-document-project 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 yesterday.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Document Project
Generate developer documentation for a completed feature or bug fix by reading plan artifacts, spec files, execution reports, and git diff to produce accurate, reference-heavy documentation.
Pipeline position:
arn-code-execute-plan -> arn-code-review-implementation -> **arn-code-document-project** -> arn-code-ship
This skill produces a single documentation file (or directory for complex projects) that captures what was actually built, how it diverges from the original plan, and where to find everything in the codebase.
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
- Specs directory -- path to the directory containing specification files
- Code patterns -- path to the directory containing stored pattern documentation
- Docs directory -- path to the directory where documentation is written
- Template version check: If
Template versionandTemplate updatesfields are present in the## Arnesssection, run the template version check procedure from${CLAUDE_PLUGIN_ROOT}/skills/arn-code-save-plan/references/template-versioning.mdbefore proceeding. If these fields are not present, treat as legacy and skip. - Ask for
PROJECT_NAMEif not provided in the trigger message. - Verify the project directory exists with reports:
<plans-dir>/<PROJECT_NAME>/reports/ - If Docs directory is not in config, default to
.arness/docs/
Step 2: Read Plan Artifacts
Read these files from <plans-dir>/<PROJECT_NAME>/:
- INTRODUCTION.md -- project overview, goals, key decisions
- SOURCE_PLAN.md -- original implementation plan
- All phase plans in
plans/PHASE_*.md-- acceptance criteria, expected files - All reports in
reports/-- implementation reports, testing reports - PROGRESS_TRACKER.json -- overall completion status (if it exists)
What ships with it
1 file 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.
- yesterday First seen · 140 lines · 101 tokens per session scan A b7594142c9b2
arn-code-document-project is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 1,379 once invoked, about $0.0005 per session on Opus 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
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agentmail
Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.
aria
Designs the data model, API contracts, and structural foundation of the system.
luna
Reviews code for objective correctness, security, and reliability.
max
Cleans up and improves existing code without changing behavior.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.