arbor-agent-tools

arbor-agent-tools is a skill for Claude Code, Codex from RUC-NLPIR/Arbor. It costs 69 tokens per session (965 once invoked), scanned A, original, Apache-2.0.

A local helper layer for managing Arbor-style experiment trees when the usual Arbor tools are unavailable. Arbor trees store hypotheses, runs, scores, and related task state.

In plain words
What is it for?
Use it to initialise runs, view constraints, store scores and evaluation commands, add hypotheses, update results, manage worktrees, and check merges.
Why use it?
It provides a consistent way to keep experiment state and evaluation results in a project instead of relying on missing host tools.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions Claude Code; mentions Codex.

Part of the Arbor plugin — 11 skills shipped together

Good fit Use it to initialise runs, view constraints, store scores and evaluation commands, add hypotheses, update results, manage worktrees, and check merges.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ruc-nlpir/arbor/arbor-agent-tools
About the project

Arbor is an autonomous research agent that proposes hypotheses, edits code, runs experiments, and retains improvements that succeed on held-out data in a growing hypothesis tree. Researchers use it to investigate problems and iteratively optimize solutions with real experiments. The catalogue skills and plugin expose Arbor's research-agent workflow to coding agents.

RUC-NLPIR/Arbor · 1,058 stars · on GitHub · ruc-nlpir.github.io

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.

Any agent
npx skills add RUC-NLPIR/Arbor --skill arbor-agent-tools
Clone the repo
git clone --depth 1 https://github.com/RUC-NLPIR/Arbor

Made for: Claude Code, Codex.

Or install Arbor, the plugin that ships this one along with the rest of its 11 skills.

Wrote 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.

agentmods badge for arbor-agent-tools

README.md
[![agentmods](https://agentmods.dev/badge/skills/ruc-nlpir/arbor/arbor-agent-tools.svg)](https://agentmods.dev/skills/ruc-nlpir/arbor/arbor-agent-tools)
Your own site
<a href="https://agentmods.dev/skills/ruc-nlpir/arbor/arbor-agent-tools"><img src="https://agentmods.dev/badge/skills/ruc-nlpir/arbor/arbor-agent-tools.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 965 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00069 $0.00965
Opus 5 $0.00034 $0.00483
Sonnet 5 $0.00014 $0.00193
Haiku 4.5 $0.00007 $0.00097

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

Security

Grade A, and why

arbor-agent-tools 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/arbor_state.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/arbor-agent-tools/SKILL.md · 75 lines

How it starts

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

Arbor Agent Tools

Use this skill when the host does not provide native Arbor tools. The bundled script stores state in the same style as open-source Arbor:

<cwd>/.arbor/sessions/<run_name>/.coordinator/idea_tree.json
<cwd>/.arbor/sessions/<run_name>/.coordinator/idea_tree.md

Script

scripts/arbor_state.py is stdlib-only.

Common commands:

TOOLS="<skill-dir>/arbor-agent-tools/scripts/arbor_state.py"
python "$TOOLS" init --cwd <project> --run-name <run> --task "<contract>"
python "$TOOLS" view --cwd <project> --run-name <run> --format constraints
python "$TOOLS" meta --cwd <project> --run-name <run> --set baseline_score=42 --set trunk_score=42
python "$TOOLS" meta --cwd <project> --run-name <run> --set "eval_cmd=cd {cwd} && bash eval.sh"
python "$TOOLS" add --cwd <project> --run-name <run> --parent-id ROOT --hypothesis "<four-line hypothesis>"
python "$TOOLS" update --cwd <project> --run-name <run> --node-id 1 --status done --score 45 --insight "..."
python "$TOOLS" worktree --cwd <project> --run-name <run> --node-id 1 --trunk <trunk_branch>
python "$TOOLS" prompt-executor --cwd <project> --run-name <run> --node-id 1 --workdir <worktree>
python "$TOOLS" prompt-executor --cwd <project> --run-name <run> --node-id 1 --smoke
python "$TOOLS" eval --cwd <project> --run-name <run> --split dev --exec-cwd <worktree> --cmd "bash {cwd}/eval.sh" --set-meta trunk
python "$TOOLS" record --cwd <project> --run-name <run> --node-id 1 --score 45 --insight "..." --result "..."
python "$TOOLS" parse-log --log <project>/run.log --metric val_bpb
python "$TOOLS" report --cwd <project> --run-name <run>
python "$TOOLS" check --cwd <project> --run-name <run> --require-report --require-experiment --require-executor-prompt

Read references/tool-mapping.md when deciding which script command maps to a native Arbor tool.

State Rules

  • Keep scores absolute.
  • Keep eval commands templated with {cwd} and {node_id}.
  • Do not run B_test during executor iteration.
  • Use record for executor outcomes so artifacts and tree updates stay in one place.
  • Use check before trusting a hand-edited tree. Add artifact flags such as --require-report, --require-experiment, --require-executor-prompt, --require-events, --require-run-stats, or --strict-artifacts when validating a completed run.
  • Serialize tree-mutating commands for the same run. Do not parallelize init, meta, add, update, prune, propagate, eval, record, worktree, or merge.

Read the full file on GitHub · 75 lines

Files

What ships with it

3 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.

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. 8d ago First seen · 75 lines · 69 tokens per session scan A e38bcb844489

Subscribe to this mod's changes

arbor-agent-tools is a skill published in the GitHub repository RUC-NLPIR/Arbor (1,058 stars, last pushed 8d ago), licensed Apache-2.0. It adds 69 tokens to every session and 965 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

skill-forge

Autonome Verbesserung nach dem Autoresearch-Paradigma (Karpathy). Zwei Modi: (1) Skill-Modus — optimiert eine SKILL.md durch iterative Mutation und Evaluation. (2) Generic-Modus — optimiert beliebige Dateien gegen jede mechanische Metrik (Testabdeckung, Bundle-Size, Lighthouse-Score, Docker-Image-Größe, etc.). Zwei…

GodModeAI2025/skill-forge · 276 tokens

autogpt-agents

Autonomous AI agent platform for building and deploying continuous agents. Use when creating visual workflow agents, deploying persistent autonomous agents, or building complex multi-step AI automation systems.

davila7/claude-code-templates · 39 tokens

autocontext-consumer

Use when an agent needs to USE knowledge Autocontext already produced - find which scenarios have knowledge, read the playbook and lessons for one, understand the on-disk file and folder layout, and move knowledge between checkouts. Host-agnostic; requires only the autoctx CLI and the filesystem.

greyhaven-ai/autocontext · 67 tokens

autocontext-creator

Use when an agent needs to CREATE knowledge with Autocontext - run a scenario or plain-language task through the improvement loop, judge or improve a single output, and inspect what the run produced. Host-agnostic; requires only the autoctx CLI.

greyhaven-ai/autocontext · 57 tokens

autocontext

Iterative strategy generation and evaluation system. Use when the user wants to evaluate agent output quality, run improvement loops, queue tasks for background evaluation, check run status, inspect runtime artifacts and session branch lineage, or discover available scenarios. Provides LLM-based judging with…

greyhaven-ai/autocontext · 60 tokens

codex-autoresearch

Triage improvement work and run or resume accepted measured loops in a local project. Architecture, documentation, UX, product study, open research, taste, and one-shot fixes stay direct unless the user explicitly requests repeated measurement with a complete experiment contract.

TheGreenCedar/codex-autoresearch · 55 tokens