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-legacy/first-tree-writenpx skills add first-tree-ai/first-tree-legacy --skill first-tree-writegit clone --depth 1 https://github.com/first-tree-ai/first-tree-legacyWrote 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-legacy/first-tree-write)<a href="https://agentmods.dev/skills/first-tree-ai/first-tree-legacy/first-tree-write"><img src="https://agentmods.dev/badge/skills/first-tree-ai/first-tree-legacy/first-tree-write.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.00073 | $0.00946 |
| Opus 5 | $0.00036 | $0.00473 |
| Sonnet 5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
first-tree-write 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Tree Write
Read these first:
../first-tree/SKILL.md../first-tree/references/anti-patterns.md../first-tree/references/maintenance.md
What This Skill Does
Take one specific source — a PR, a doc, a note — and produce zero, one, or a small set of tree changes that capture what's durable and decision- relevant. The output is a tree-repo PR linked to the source.
When To Use This Skill
| Use this skill | Use a different skill |
|---|---|
| User pastes a PR link and says "reflect this in the tree" | User asks "is the tree up to date?" → first-tree-sync |
| User pastes a meeting note about a decision | Repo is unbound → first-tree-onboarding first |
| User pastes raw text and asks for the tree implication | A GitHub notification needs only a label / comment → first-tree-github-scan |
GitHub Scan agent classifies a notification as route=write |
Audit drift since a release → first-tree-sync |
The Default Stance
Default to not writing. The tree compresses expensive context; a node nobody reads is worse than a missing node. If the source does not clearly establish a decision, constraint, ownership change, or cross-domain relationship, write nothing and tell the user why.
How To Run
| Phase | Reference |
|---|---|
| Decide what is tree-worthy | references/what-belongs.md |
| Draft the update | references/workflow.md |
| Shape the tree node | references/node-shape.md |
| Decide between write and sync | references/boundary.md |
What ships with it
6 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.
- 5d ago First seen · 86 lines · 73 tokens per session scan A a0a25d914431
first-tree-write is a skill published in the GitHub repository first-tree-ai/first-tree-legacy (47 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 946 once invoked, about $0.0004 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
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
user-general-facts
Capture and organize general facts about the user by topic.
daily-logs
Track daily activity logs and summaries for the user. TRIGGER BY: read/edit user memory.
aidd-context:02:project-init
Initialize or refresh the project memory bank, scaffold the rules directory, and ensure AI context files contain the project memory block. Use when running aidd init for the first time, bootstrapping a new project, or re-running the init flow on an existing project. Do NOT use for updating individual memory files…
02-project-memory
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.