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/skymanbp/cc-tree/treenpx skills add skymanbp/cc-tree --skill treegit clone --depth 1 https://github.com/skymanbp/cc-treeWhat 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.00247 | $0.04252 |
| Opus 5 | $0.00123 | $0.02126 |
| Sonnet 5 | $0.00049 | $0.00850 |
| Haiku 4.5 | $0.00025 | $0.00425 |
Grade A, and why
tree 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tree — universal radial-tree exploration engine
What this skill is. A single engine implementing recursive radial-tree exploration (root → 12-framing expansion → per-node 12-field derivation → score → recurse on high-verdict leaves → terminate on substantive convergence). What varies between use-cases (brainstorm vs critique vs design vs code-audit) is the baseline recipe, node schema, scoring dimensions, and verdict vocabulary — all parameterized via a preset file.
What this skill is NOT. Not a one-shot LLM call that returns a bulleted list. Not a chat interface — once
/cc-tree:treeis invoked, the engine runs to convergence without further prompts. Not bundled with a model — pure prompt-engineering on top of Claude Code's existing model setting.
The full engine specification lives in docs/ENGINE.md.
This SKILL.md is a 7-step navigation guide; Read docs/ENGINE.md
before producing the first node (the engine spec is what defines
"valid" for everything you'll write).
1. Invocation
/cc-tree:tree <root> --preset <name|path> [flags]
<root> is preset-typed:
brainstormpreset → topic string, e.g."ways to detect dark-matter substructure"attackpreset → file path (.md/.tex/ etc.) or quoted argument-textdesignpreset → design-prompt string or.mdfile pathcode-auditpreset → file path or directory path
--preset is required:
- Built-in:
brainstorm,attack,design,code-audit(resolve topresets/<name>.mdin this plugin) - Path:
./my-custom.md(any .md file with the right frontmatter)
Common flags (apply across presets)
| Flag | Default | Meaning |
|---|---|---|
--lang <tag|auto> |
en | Output language for all localized prose (node statements, derivations, report narrative, warnings). Machine tokens — flag/command names, frontmatter & JSON keys, root_kind values, verdict labels, status tokens, filenames — always stay English. <tag> is a BCP-47-like code (en, zh, zh-Hans, zh-Hant, fr-CA); zh = Simplified Chinese, zh-Hant = Traditional. auto detects the dominant language of <root> and falls back to en for mixed / path-only / code-only input. Resolved once before preset load, recorded in run metadata (language_request / output_language / language_source), and never prompted mid-run. Full precedence, resume, and chain semantics: docs/ENGINE.md §1.0. |
--width N |
∞ | Cap on final leaf count (the outer arc of the tree). ∞ / inf / unspecified all mean unlimited. |
--depth N |
∞ | Cap on tree depth from root. |
--rounds N |
conv |
Cap on expansion rounds. conv = no cap; terminate by §6 substantive convergence. |
--max-branches N |
∞ | Cap on new branches per node per round. Floor is 12 because §3 requires all 12 framings to fire; this flag only raises the ceiling. |
--out <dir> |
tree-out/<UTCdate>__<slug>/ |
Output directory. Per-preset commands override (e.g. brainstorm-out/). |
--glossary <path> |
(preset-determined) | Path to a glossary / FACTS.md / glossary section in a dossier; used by §2.0 grill prelude. |
--field <name|path> |
(none) | Field profile for domain-aware reviewer weighting. <name> → field-profiles/<name>.md in this plugin; <path> → a literal file. Feeds §3.C / §3.D / §3.I / §3.J + the §3.X / §4 evidence bar. Missing profile → warn + continue (non-blocking). See docs/ENGINE.md §2.2. |
--seed-from <primary.md> |
(none) | Seed the tree from a prior run's primary deliverable (shortlist.md / options.md / confirmed.md): each listed item enters as a depth-1 seed node and is re-expanded. The substrate for cross-preset chaining (docs/chaining.md). Alias: --from-prior. |
--no-grill |
off | Skip §2.0 glossary grill prelude. Marks root-node terms as unverified; §6 convergence adds a warning. |
--no-online |
off | Disable WebSearch / WebFetch. Local + already-Read references only. |
--min-frameworks N |
12 | Minimum framing passes per node. Floor is 12 (full §3.A–§3.L); flag exists for documentation, not relaxation. |
--min-novelty-ratio R |
0.15 | §6.1 condition 2 requires "last 2 rounds' high-verdict / total < R". |
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 · 273 lines · 247 tokens per session scan A 04e9a0360649
tree is a skill published in the GitHub repository skymanbp/cc-tree (108 stars, last pushed 7d ago), licensed MIT. It adds 247 tokens to every session and 4,252 once invoked, about $0.0012 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…