forestui: Instructions file for Claude Code

CLAUDE.md

forestui CLAUDE.md is an instructions file for Claude Code from flipbit03/forestui. It costs 9,008 tokens per session, scanned A, original, MIT.

A project instruction file for AI coding assistants working on ForestUI. It describes the project, its technology, its file structure, and a strict rule not to interact with the user's live tmux session.

In plain words
What is it for?
Use it as operating guidance when an AI assistant edits or tests the ForestUI codebase.
Why use it?
It prevents an assistant from disturbing active editors, terminals, or conversations while working in the repository. It also provides project-specific context before changes are made.

Instructions file for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is flipbit03/forestui's own configuration. It tells Claude Code how to work on forestui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything forestui configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is git fetch && git worktree add -b <branch> ../forestui-<topic> origin/main.

Reuse

Borrowing it

Nothing to install: this file belongs to flipbit03/forestui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/flipbit03/forestui/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/flipbit03/forestui

Made for: Claude Code.

Wrote 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.

agentmods badge for forestui CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/flipbit03/forestui/claude-md/github.svg)](https://agentmods.dev/instructions/flipbit03/forestui/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/flipbit03/forestui/claude-md"><img src="https://agentmods.dev/badge/instructions/flipbit03/forestui/claude-md/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.

agentmods 80×15 button for forestui CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/flipbit03/forestui/claude-md"><img src="https://agentmods.dev/badge/instructions/flipbit03/forestui/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9,008 This file is loaded in full into every session.
When invoked 9,008 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.09008 $0.09008
Opus 5.5 $0.03603 $0.03603
Sonnet 5.5 $0.01802 $0.01802
Haiku 4.5 $0.00901 $0.00901

Measured 1mo ago against content hash ecf4ae2cfa50, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

forestui CLAUDE.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 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.

CLAUDE.md · 687 lines

How it starts

The opening of the file, as written. The whole thing — 687 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md - AI Development Guidelines

This file provides context for AI assistants (like Claude) working on forestui.

Never touch the user's live tmux

This rule applies to every task in this repo, not just testing.

Whoever works on forestui is, almost by definition, running forestui. That is what makes this different from an ordinary "be careful" note: a live tmux server is up right now, holding their actual work — editors mid-edit, terminals mid-command, Claude sessions mid-conversation, laid out the way they left them. It is not a risk to weigh against convenience; it is the default state of this repo's development environment, and a bare tmux command from a shell attaches straight to it.

The session running this task is very likely one of those windows — forestui opens Claude sessions in tmux windows, and this is a Claude session. A stray rename-window, kill-window or kill-server can destroy the user's work, up to and including the conversation that issued the command.

  • Never run a bare tmux command — not to look, not to list, not "just once". tmux list-sessions is as dangerous as tmux kill-server, because it is the step that convinces you the next call is safe.
  • Drive tmux only through tu, with TMUX_TMPDIR pointed at a throwaway directory. The test-forestui skill has the exact invocation.
  • Exploring tmux behaviour is not an exception. Learning what a tmux command does, probing options or hooks, reproducing something from the docs — all of it goes on an isolated server under tu. A separate -L socket looks like it solves this, and it does not: it relies on never once forgetting the flag, against a default that reaches the user's live session.

The test-forestui skill carries the full harness recipe, and its description asks to be loaded before any tmux command, not only before testing — because tasks that do not look like testing are exactly where this gets broken: a spike, doc research, "just checking how tmux options work". The rule is repeated here because this file is always loaded and a skill is not.

Read the full file on GitHub · 687 lines

Changes

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.

  1. 1mo ago Changed · +59 lines · +967 tokens per session ecf4ae2cfa50
  2. 1mo ago First seen · 628 lines · 8,041 tokens per session scan A 88fa50304988

Subscribe to this mod's changes

forestui CLAUDE.md is an instructions file published in the GitHub repository flipbit03/forestui (26 stars, last pushed 14d ago), licensed MIT. It adds 9,008 tokens to every session, about $0.0360 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens