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/first-tree-ai/first-tree/first-tree-readnpx skills add first-tree-ai/first-tree --skill first-tree-readgit clone --depth 1 https://github.com/first-tree-ai/first-treeWrote 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.
[](https://agentmods.dev/skills/first-tree-ai/first-tree/first-tree-read)<a href="https://agentmods.dev/skills/first-tree-ai/first-tree/first-tree-read"><img src="https://agentmods.dev/badge/skills/first-tree-ai/first-tree/first-tree-read.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00068 | $0.00741 |
| Opus 5 | $0.00034 | $0.00370 |
| Sonnet 5 | $0.00014 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
first-tree-read 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Tree Read — Local Context
Purpose and authority
Read the current Agent's private Local Context before acting on a task with a
repo, path, feature, domain, owner, bug, or error signal. This payload is the
managed Local variant of first-tree-read; its public name and routing
description intentionally match the Remote payload.
Local Context is host-local truth for this Agent only. It is not Team-approved
truth, a Git checkout, a BYO snapshot, or a fallback for an unreadable or
invalid remote binding. first-tree-seed, context-tree-review, and
context-tree-audit never operate on it.
Apply the generated Context Tree Policy's normal/archive/member authority and code-vs-tree drift rules. Never modify Tree content with this Skill.
Workflow
-
Run the generated briefing's exact First Tree CLI invocation:
<firstTreeInvocation> --json tree local resolve --ensure --intent readUse only the returned
data.path. The guard accepts no caller-supplied live path and rechecks runtime identity, fixed Workspace containment, resource limits, the remote-observed latch, and the live Server binding. Missing, corrupt, unknown, invalid, frozen, or bound state stops the Local read. -
Before reading business Context, run:
<firstTreeInvocation> tree verify --tree-path "<live-root>"A non-zero result stops the read. Report that Local Write must repair the live Tree; do not guess an older version or continue from partial files.
-
Inspect the filesystem hierarchy command from the live root, then use its selectors before native Markdown reads:
<firstTreeInvocation> tree tree --tree-path "<live-root>" --help <firstTreeInvocation> tree tree --tree-path "<live-root>" [path] [selectors]This mode performs no Git discovery, pull, branch, commit, snapshot, forge, Cloud Tree IO, or attribution. Keep the read focused: root and relevant parents, matched leaves, and material
soft_linksonly.
What ships with it
2 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.
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.
- 4d ago First seen · 78 lines · 68 tokens per session scan A b9b82339d5c8
first-tree-read is a skill published in the GitHub repository first-tree-ai/first-tree (140 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 741 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.
Other skills, from other repositories
github-scan
Operate the first-tree github scan CLI — the GitHub notification daemon and inbox runtime. Use whenever you need to run, start, stop, inspect, poll, or debug github-scan; view or respond to GitHub-triggered work from the terminal; or wire up the github-scan statusline hook.
first-tree-sync
Audit and repair drift between merged code and the Context Tree in both directions — tree→code (does code still support tree facts?) and code→tree (does the tree register everything code now contains?). Use when the tree may be stale, wrong, outdated, or missing coverage for recent code changes; after a large merge…
first-tree-github-scan
Agent skill for handling a single GitHub notification spawned by the First Tree github-scan daemon. Use when an agent needs to decide how to tag, comment on, escalate, or hand off a PR, issue, review request, mention, or CI event, and when it needs to choose between handling on GitHub or routing to first-tree-sync /…
first-tree-write
Write Context Tree updates from explicit source material — code PRs, design docs, meeting notes, raw text. Use when the user gives you a concrete source and wants the right durable tree change drafted, linked, and reviewed. This skill is source-driven and targeted; use first-tree-sync instead for broad drift audits…
first-tree
Canonical whitepaper and routing skill for First Tree. Explains what belongs in a Context Tree, how source or workspace roots, tree repos, and bindings relate, and how the current first-tree tree and first-tree github scan surfaces fit together. Use when you need shared First Tree concepts, need to choose between…
first-tree-onboarding
One-shot onboarding command for First Tree. Drives a repo or workspace from "no first-tree" all the way to "tree bound, real content drafted, daemon running, agent templates confirmed" — end to end, in one skill invocation. Trigger this skill when the user invokes /first-tree-onboarding, says "onboard this repo to…