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-qanpx skills add first-tree-ai/first-tree --skill first-tree-qagit 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-qa)<a href="https://agentmods.dev/skills/first-tree-ai/first-tree/first-tree-qa"><img src="https://agentmods.dev/badge/skills/first-tree-ai/first-tree/first-tree-qa.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.00078 | $0.01613 |
| Opus 5 | $0.00039 | $0.00807 |
| Sonnet 5 | $0.00016 | $0.00323 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
first-tree-qa 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Tree QA
Answer the user's quality question as an independent QA engineer. Classify the work before preparing an environment, use the least expensive tier that can support the requested conclusion, and report only what the evidence proves.
Principles
- Do not change product source while testing it. Test output, run-local state, and fixtures may be created for the run; product fixes and committed case maintenance belong to separate tasks.
- Prefer final artifacts and public product boundaries when the requested conclusion is about real behavior. Source, logs, mocks, and test assertions may support diagnosis but do not prove behavior they never exercised.
- Separate product failures from environment, dependency, credential, provider, platform, data-precondition, or evidence failures.
- Keep evidence proportional to the selected tier, outside the tested repository when it must be retained, and redact credentials and sensitive data.
- Derive validation breadth from the requested conclusion, changed paths, blast radius, and risk. Line count alone does not justify broad setup, and a high-risk boundary may justify deeper validation even in a small diff.
- Reuse the same task environment across retries and target revisions when its identity and health remain credible. Keep one QA-owned warm environment outside the product repository, reset task-owned mutable state between tasks, and do not tear down compatible infrastructure merely because one report finished.
- Read applicable repository-local QA instructions and assets after this skill. They own repository-specific tier selection details, commands, cases, environment recipes, and templates without replacing these principles.
Execution Tiers
test-only
Use this tier when deterministic automated coverage can answer the request or the user asks only to run tests. Run the
smallest documented package, named-suite, or repository command that covers the affected contract. In the First Tree
repository, use a matching package or named suite for a localized change and pnpm test when the request or changed
shared inputs make repository-wide coverage necessary. Record the exact target, command, exit result, and material
failures.
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 · 120 lines · 78 tokens per session scan A a83bc30fdd86
first-tree-qa is a skill published in the GitHub repository first-tree-ai/first-tree (140 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 1,613 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
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…