setup

A setup command for OpenArche, a Claude Code plugin that manages complex coding tasks through planning and closeout steps.

In plain words
What is it for?
Use it to initialize OpenArche, check its installation, locate its global settings, and understand where repository task data is stored.
Why use it?
It checks whether the plugin is installed correctly and explains what will happen after setup, reducing confusion about configuration and saved task state.

Command

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 commands/done-0/openarche/setup
Clone the repo
git clone --depth 1 https://github.com/Done-0/openarche
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,233 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00011 $0.03233
Opus 5 $0.00005 $0.01617
Sonnet 5 $0.00002 $0.00647
Haiku 4.5 $0.00001 $0.00323

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

Security

Grade A, and why

setup scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const {execSync}=require('child_process');
commands/setup.md · 348 lines

How it starts

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

Initialize OpenArche in a way a first-time user can understand.

Keep the explanation short and practical:

  • what OpenArche will start doing automatically after setup
  • why complex tasks will be handled differently
  • whether the plugin is ready
  • what the user should do next
  • where global state lives and where repository task state will appear

Only mention Claude Code internal hook names when you are editing settings.json or showing exact config keys.

Step 0: Ghost Install Check

node -e "
const fs=require('fs'),path=require('path'),os=require('os');
const base=path.join(os.homedir(),'.claude','plugins','cache','openarche');
const reg=path.join(os.homedir(),'.claude','plugins','installed_plugins.json');
const hasCache=fs.existsSync(base);
let hasReg=false;
try{hasReg=fs.readFileSync(reg,'utf8').includes('openarche');}catch{}
console.log('Cache:',hasCache?'YES':'NO','Registry:',hasReg?'YES':'NO');
"
  • Cache=YES, Registry=NO: delete the cache directory, then tell the user to reinstall
  • Cache=NO, Registry=YES: remove the openarche entry from installed_plugins.json
  • Otherwise: continue

Step 1: Detect Runtime

node -e "console.log(process.execPath)"

If node is not available, stop and tell the user to install Node.js (https://nodejs.org).

Save the node executable path. You will use it in Step 4.

Step 2: Build Plugin

Find the plugin directory:

node -e "
const fs=require('fs'),path=require('path'),os=require('os');
const cacheDir=path.join(os.homedir(),'.claude','plugins','cache','openarche','openarche');
try{
  const versions=fs.readdirSync(cacheDir).sort();
  console.log(path.join(cacheDir,versions[versions.length-1]));
}catch{console.log('NOT_FOUND');}
"

Save this as PLUGIN_DIR. If it returns NOT_FOUND, tell the user to run /plugin install openarche first.

Check if dist/ exists (replace PLUGIN_DIR with the actual path obtained above):

node -e "console.log(require('fs').existsSync(require('path').join('PLUGIN_DIR','dist'))?'EXISTS':'MISSING');"

Read the full file on GitHub · 348 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 · 348 lines · 11 tokens per session scan A dbf6ad660ffc

Subscribe to this mod's changes

setup is a command published in the GitHub repository Done-0/openarche (12 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 3,233 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.