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 instructions/first-tree-ai/first-tree-legacy/agents-mdgit 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/instructions/first-tree-ai/first-tree-legacy/agents-md)<a href="https://agentmods.dev/instructions/first-tree-ai/first-tree-legacy/agents-md"><img src="https://agentmods.dev/badge/instructions/first-tree-ai/first-tree-legacy/agents-md.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.00673 | $0.00673 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
first-tree-legacy AGENTS.md 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a small pnpm workspace for first-tree. The root
package.json holds workspace-level metadata and scripts, while
pnpm-workspace.yaml includes apps/* and packages/*. The CLI package lives
in apps/cli/ and is published as first-tree. Put future shared libraries in
packages/<name>/. Keep package-specific source, tests, and assets inside the
owning package, for example apps/cli/src/, apps/cli/tests/, and
apps/cli/assets/.
Build, Test, and Development Commands
pnpm install: install workspace dependencies with the pinned pnpm version.pnpm -r test: run every package test script. Current test scripts are placeholders and fail until real tests are added.pnpm --filter first-tree test: run only the CLI package tests once implemented.- Add package-level
build,typecheck, andlintscripts before introducing compiled TypeScript or lint gates; expose root scripts throughpnpm -r.
Coding Style & Naming Conventions
Use English for code, comments, identifiers, commit messages, and technical
documentation. Prefer small modules with explicit exports. For JavaScript or
TypeScript, use 2-space indentation, camelCase for functions and variables,
PascalCase for classes and types, and kebab-case for command names,
workspace package names, and directories. Keep the root package thin; product
code should live in apps/ or packages/.
Testing Guidelines
No test framework is configured yet. When adding implementation, add tests in
the same workspace package and wire them through that package's test script.
Use *.test.ts or *.test.js naming, and prefer focused unit coverage for CLI
command parsing, filesystem behavior, and workspace validation. Add regression
tests with every bug fix.
Commit & Pull Request Guidelines
Recent history is brief and includes feat: init pnpm workspace; prefer
Conventional Commits such as feat: add cli entry, fix: handle missing config,
or docs: update contributor guide. Keep subjects concise and imperative.
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 · 62 lines · 673 tokens per session scan A d6ed91b5db76
first-tree-legacy AGENTS.md is an instructions file published in the GitHub repository first-tree-ai/first-tree-legacy (47 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 673 tokens to every session, about $0.0034 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 instructions, from other repositories
cocoindex AGENTS.md
AGENTS.md instructions for cocoindex-io/cocoindex, covering agents.md, build and test commands, building, testing and code formatting and linting.
apm python.instructions.md
Python development guidelines.
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
packmind packmind-rest-api-endpoint-design.instructions.md
Instructions for PackmindHub/packmind: Conventions for designing REST API endpoints that are predictable, self-documenting, and aligned with distinct business actions. Favors dedicated action endpoints over generic status updates, and rout... .
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
Meterless AGENTS.md
Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.