arn-code-taskify

A command that turns a structured TASKS.md project plan into a Claude Code task list with dependencies. Dependencies show which tasks must be completed before others can start.

In plain words
What is it for?
Use it to convert an Arness project plan into executable Claude Code tasks and connect related tasks in a dependency graph.
Why use it?
It saves time when moving from project planning to execution and makes task order visible. It creates the list but does not execute or assign the tasks.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/appsvortex/arness/arn-code-taskify
Any agent
npx skills add AppsVortex/arness --skill arn-code-taskify
Clone the repo
git clone --depth 1 https://github.com/AppsVortex/arness

Made for: Claude Code, Codex.

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,654 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00081 $0.01654
Opus 5 $0.00041 $0.00827
Sonnet 5 $0.00016 $0.00331
Haiku 4.5 $0.00008 $0.00165

Measured 2d ago against content hash 530273e7b1db, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

arn-code-taskify 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 2d 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.

plugins/arn-code/skills/arn-code-taskify/SKILL.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Arness Taskify

Convert a project's TASKS.md into a Claude Code task list with dependency management. Reads the structured task definitions created by arn-code-save-plan, creates Claude Code tasks via TaskCreate, and wires up the dependency graph via TaskUpdate.

This skill does NOT execute tasks or assign them to agents — it only creates the task list. Execution happens after the task list is created, either manually or through Claude Code's task system.

Workflow

Step 1: Load the Project

Read the project's CLAUDE.md and look for a ## Arness section. Extract:

  • Plans directory — base path where project plans are saved

If ## Arness is not found: inform the user: "Arness is not configured for this project yet. Run /arn-planning to get started — it will set everything up automatically." Do not proceed.

Deferred Task List Setup:

Check for Task list ID in ## Arness config. If present: verify CLAUDE_CODE_TASK_LIST_ID environment variable is set and matches. If not set or mismatched, warn: "Task list ID is configured as <id> in ## Arness but CLAUDE_CODE_TASK_LIST_ID is not set in the current environment. Tasks may not persist across sessions. Verify .claude/settings.json contains the correct env setting."

If absent:

Ask (using AskUserQuestion):

"Persistent task lists are not configured. Would you like to enable them? (Recommended — tasks survive across sessions)"

  1. Yes (Recommended) — Auto-generate ID from project directory name
  2. Yes, with custom ID — Specify the task list ID
  3. No — Keep tasks session-scoped

If Yes: derive ID (slugify project directory name or use custom ID), write to .claude/settings.json (create if needed, preserve existing env vars), add Task list ID to ## Arness config. Inform: "Persistent task list configured."

If No: proceed without persistence. Inform (once): "Tasks will be session-scoped. Enable persistence anytime with /arn-code-taskify."

Ask the user for PROJECT_NAME if not provided in the conversation.

Read the full file on GitHub · 172 lines

Changes

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.

  1. 2d ago First seen · 172 lines · 81 tokens per session scan A 530273e7b1db

Subscribe to this mod's changes

arn-code-taskify is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,654 once invoked, about $0.0004 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.