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.
git clone --depth 1 https://github.com/AutomateLab-tech/agency-osWrote 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/commands/automatelab-tech/agency-os/tree)<a href="https://agentmods.dev/commands/automatelab-tech/agency-os/tree"><img src="https://agentmods.dev/badge/commands/automatelab-tech/agency-os/tree/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/automatelab-tech/agency-os/tree"><img src="https://agentmods.dev/badge/commands/automatelab-tech/agency-os/tree.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00421 |
| Opus 5.5 | $0.00000 | $0.00168 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
tree 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 1mo 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.
What it actually says
Command: tree [--depth N] [--corpus=<s>] [--status=<s>]
Emit a compact indented view of the active task hierarchy and refresh state/task-tree.json. This is the primary tool for understanding the board's shape before adding new work.
Default scope: all non-terminal rows (Suggestion, Discussion, To-Do, In Progress). --status filters to a specific status. --corpus narrows to one corpus. --depth N truncates at N levels (default: unlimited).
-
Sync preflight (this also writes
task-tree.jsonas a side-effect — see Sync section in SKILL.md). -
Build the tree from the live result: group rows by
Parent Task, render depth-indented. -
Output as plain markdown (links clickable, not a fenced block):
[OS-12](url) "Top-level initiative" [In Progress · General · L] [OS-13](url) "Container subtask" [To-Do · M] [OS-14](url) "Leaf work item" [To-Do · S] [OS-15](url) "Another subtask" [Suggestion · M] [OS-16](url) "Unrelated top-level" [To-Do · Recurring · M] -
After the tree, print a one-line summary:
<N> tasks across <K> top-level roots (snapshot written to state/task-tree.json).
When to call tree:
- At the start of any session where you'll be adding or reorganizing tasks.
- Before any batch
suggestoperation, ifstate/task-tree.jsonis absent or you're unsure of the current shape. - Whenever the user asks "what's the structure", "show me the hierarchy", "how is this organized".
tree is a read-only command — it never mutates Notion, only refreshes the local snapshot.
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.
- 1mo ago First seen · 27 lines · 0 tokens per session scan A 9601616e2f64
tree is a command published in the GitHub repository AutomateLab-tech/agency-os (3 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 421 tokens. 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-31.
Other commands, from other repositories
p9
A Tech Lead mode for writing prompts and managing the P8 team. A Tech Lead guides technical work and breaks projects into tasks.
architecture-note
Record a brief Architecture Decision Record (ADR) about a recent technical choice.
write-handoff
Generate a dense state-restoration document before ending a session.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.