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-syncnpx skills add first-tree-ai/first-tree-legacy --skill first-tree-syncgit 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-sync)<a href="https://agentmods.dev/skills/first-tree-ai/first-tree-legacy/first-tree-sync"><img src="https://agentmods.dev/badge/skills/first-tree-ai/first-tree-legacy/first-tree-sync.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.1 | $0.00137 | $0.01367 |
| Opus 5 | $0.00068 | $0.00683 |
| Sonnet 5 | $0.00027 | $0.00273 |
| Haiku 4.5 | $0.00014 | $0.00137 |
Grade A, and why
first-tree-sync 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Tree Sync
Read these first:
../first-tree/SKILL.md../first-tree/references/functions.md../first-tree/references/maintenance.md
What This Skill Does
Compare a Context Tree against the source repo(s) it describes in both directions:
- tree→code — for each tree node, does the code still support it?
(catches
tree-stale,tree-wrong,tree-outdated,cross-domain-broken,ownership-stale) - code→tree — for each piece of source structure, does the tree
register it? (catches
code-not-synced)
Classify every gap, then route each finding to auto-fix, hand-off-to-write, needs-human, or skip.
Two phases, in order:
- audit — produce a
drifts[]list. Read-only, human-paced. Combines a tree→code pass (Phase 1–3) with a code→tree sweep (Phase 4). - fix — for each drift, decide auto-fix / write-handoff / needs-human / skip and act on that decision.
Each phase has a dedicated reference; follow them in order.
When To Use This Skill
| Use this skill | Use a different skill |
|---|---|
| User asks "is the tree up to date?" | User has a specific PR / doc to reflect into the tree → first-tree-write |
| Audit drift since a release | Repo is unbound → first-tree-onboarding first |
GitHub Scan agent routed a notification route=sync |
Notification needs a label / comment only → first-tree-github-scan keeps ownership |
The Six Drift Types
tree-stale — tree node was true; code moved
tree-wrong — tree node never matched code
tree-outdated — superseded by a newer decision
code-not-synced/structural — code structure exists; tree skeleton does not register it
code-not-synced/substantive — code decision/constraint exists; tree does not record it
cross-domain-broken — soft_links target gone or wrong
ownership-stale — owners list no longer matches reality
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 · 121 lines · 137 tokens per session scan A 31e74c42c18f
first-tree-sync 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 137 tokens to every session and 1,367 once invoked, about $0.0007 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/.
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
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.
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…
daily-logs
Track daily activity logs and summaries for the user. TRIGGER BY: read/edit user memory.