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 skills add fmflurry/settings-opencode --skill treetopiagit clone --depth 1 https://github.com/fmflurry/settings-opencodeWrote 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/fmflurry/settings-opencode/treetopia)<a href="https://agentmods.dev/skills/fmflurry/settings-opencode/treetopia"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/treetopia/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/skills/fmflurry/settings-opencode/treetopia"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/treetopia.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 105 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00051 | $0.00927 |
| Opus 5.5 | $0.00020 | $0.00371 |
| Sonnet 5.5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
treetopia 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Treetopia
Create an isolated OpenCode worktree whenever the user explicitly wants branch isolation, parallel feature work, or protection from branch collisions.
Trigger Rules
Use this skill only when the user explicitly says one of these intents:
- Create a worktree.
- Use a worktree.
- Use an isolated worktree.
- Create a parallel feature branch.
- Avoid branch collision.
- Keep two agents or two features from sharing one branch.
Do not use this skill merely because the user asks for normal implementation, refactor, testing, or feature work. Ordinary feature work stays in the current checkout unless the user explicitly requests isolation.
Purpose
Prevent two primary agents or two active features from sharing the same branch and overwriting or colliding with each other's changes.
Start Workflow
When triggered:
- Derive a concise branch name from the user's task.
- Use lowercase words separated by hyphens.
- Prefer a short prefix such as
feature/,fix/, orchore/when obvious. - Keep the name specific enough to identify the task.
- Determine the base branch.
- If the user names a base branch, use that branch.
- Otherwise, default to the current branch.
- Immediately call
worktree_create.- Pass the derived branch name.
- Pass the base branch only when the user named one or the tool requires it.
- Continue development inside the new worktree/session created by the tool.
Example tool intent:
worktree_create(branch: "feature/customer-import", baseBranch: "main")
If no base branch was named:
worktree_create(branch: "fix/login-timeout")
Development Guidance Inside Worktree
- Treat the worktree as the isolated task workspace.
- Follow normal project instructions, architecture rules, and verification gates.
- Do not assume the original checkout has your worktree changes.
- Avoid cross-worktree edits unless the user explicitly asks.
- Preserve the verification gate before proposing teardown, merge, or cleanup.
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 · 111 lines · 51 tokens per session scan A 957de7ba9e0c
treetopia is a skill published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 927 once invoked, about $0.0002 per session on Opus 5.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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…