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/phenomenoner/adaptive-agent-harness/aar-ipython-codegraphnpx skills add phenomenoner/adaptive-agent-harness --skill aar-ipython-codegraphgit clone --depth 1 https://github.com/phenomenoner/adaptive-agent-harnessWhat 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.00067 | $0.00682 |
| Opus 5 | $0.00034 | $0.00341 |
| Sonnet 5 | $0.00013 | $0.00136 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
aar-ipython-codegraph 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AAR IPython CodeGraph
This is an optional external workflow. It is not a workspace backend, broker provider, authority source, or part of AAR core. Never install CodeGraph, alter host configuration, or initialize an index merely because this skill is present; use it only when the caller chose the workflow and a CodeGraph command or tool is already available.
Establish the artifact boundary
- Use
$aar-operationsandaar_capabilitiesto confirm the current runtime, tool surface, artifact schema, and operation binding. - Obtain complete artifact references from a programmable workspace result, checkpoint manifest,
RLM trace, or operation receipt. Resolve each selected reference through
aar_artifact_resolvewith an explicitmax_byteslimit andallow_redacted=trueonly when disclosure is authorized. - Verify artifact ID, SHA-256 digest, media type, size, creating operation, and redaction state
before decoding
content_base64. Reject any mismatch. - Materialize only source-like, non-secret content into a task-local navigation directory. Keep a manifest mapping each safe relative filename to its original AAR artifact reference and digest.
Do not index the live .aar database, SQLite WAL files, worker sockets, checkpoint stores,
credential locations, private evidence trees, runtime homes, or an entire user directory. Do not
materialize arbitrary pickle data. A checkpoint exclusion is not permission to disclose it.
Build or refresh the external graph
- Prefer a current task-local
.codegraph/index. Use the callable CodeGraph exploration tool when the host exposes it; otherwise use the installedcodegraph status,codegraph init,codegraph sync, andcodegraph explorecommands. - Initialize only the bounded materialized source root. Refresh after its manifest or source bytes
change. Keep
.codegraph/ignored and outside AAR evidence, release, and checkpoint contracts. - Ask structural questions with exact artifact filenames, symbols, or call paths. Use the graph to navigate, then read the referenced artifact bytes before making a correctness claim.
- Preserve artifact digests beside any answer derived from the graph. CodeGraph catalog, status, or index presence proves navigation metadata only; it does not prove artifact authenticity, runtime activation, execution, authority, or delivery.
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.
- 2d ago First seen · 52 lines · 67 tokens per session scan A 77ec795673a9
aar-ipython-codegraph is a skill published in the GitHub repository phenomenoner/adaptive-agent-harness (1 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 682 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-31.
Other skills, from other repositories
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram…
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue"…
migrating-workflow-v4-to-v5
Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId…
workflow-init
Install and configure Vercel Workflow SDK before it exists in nodemodules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite.
security-observability
只读查询 agent-sec-cli 已落盘的历史安全事件记录，并据此生成会话级安全复盘。仅当用户显式要求查看或审计已发生的安全事件、安全告警、安全审计记录，或要求按 session/run/trace/时间/类别筛选与统计已有安全事件，或要求复盘某次会话的安全判定时使用。不用于扫描新内容：检查代码安全性用 code-scanner，检测 prompt 注入用 prompt-scanner，审查 Skill 安全状态用 skill-ledger。不要因为对话中出现“安全”“工具调用”等字样、或为了主动自查而触发。.
internal-dev-workbench
Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated . .localhost URLs for the Next.js workbench and the observability UI, plus a Claude statusline that surfaces those URLs. Use only when the user asks for a "portless dev session", a "tmux dev layout for workflow"…