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.
curl -O https://raw.githubusercontent.com/flipbit03/forestui/main/.claude/skills/test-forestui/SKILL.mdgit clone --depth 1 https://github.com/flipbit03/forestuiWrote 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/flipbit03/forestui/test-forestui)<a href="https://agentmods.dev/skills/flipbit03/forestui/test-forestui"><img src="https://agentmods.dev/badge/skills/flipbit03/forestui/test-forestui/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/flipbit03/forestui/test-forestui"><img src="https://agentmods.dev/badge/skills/flipbit03/forestui/test-forestui.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.02152 |
| Opus 5.5 | $0.00000 | $0.00861 |
| Sonnet 5.5 | $0.00000 | $0.00430 |
| Haiku 4.5 | $0.00000 | $0.00215 |
Grade C, and why
test-forestui scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf $FUI_TEST_DIR How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-drive forestui with tu
You can launch, see, and interact with forestui in headless virtual terminals
using tu (terminal-use). This gives you the ability to visually verify your
own code changes without the user needing to test manually.
Use this whenever you're developing forestui and want to confirm your changes work. Design your own test approach based on what you changed — there is no fixed test suite. You are the tester.
FIRST: bootstrap context
Before doing ANYTHING else, run these two commands and read their output. Do NOT skip. Do NOT proceed until both are in context.
tu usage
cat ~/.tmux.conf 2>/dev/null || echo "NO_TMUX_CONF"
From tu usage: learn all commands, key syntax, wait conditions.
From .tmux.conf: learn the user's tmux prefix and all keybindings.
Translate tmux bind syntax to tu press key names yourself from these two sources.
If no .tmux.conf: defaults are prefix Ctrl+B, next Ctrl+B n, prev Ctrl+B p.
How to launch forestui
Build first. forestui is a Rust binary and ensure_tmux re-executes it, so
you must drive the built executable, not cargo run:
export PATH="$HOME/.cargo/bin:$PATH"
cargo build # in the project root
FUI_CMD=<project-root>/target/debug/forestui
NEVER launch forestui or any tmux command without TMUX_TMPDIR isolation.
NEVER call tmux directly from Bash — not even with TMUX_TMPDIR set. The
user is likely running their own tmux/forestui session right now. Any direct
tmux call risks connecting to (and corrupting) their live session. ALL
interaction with the test tmux must go through tu commands.
FUI_TEST_DIR=$(mktemp -d)
tu run --name fui --env TMUX_TMPDIR=$FUI_TEST_DIR \
--cwd <project-root> -- env -u TMUX $FUI_CMD
tu wait --name fui --text "forestui" --timeout 15000
Pass a throwaway forest directory as an argument ($FUI_CMD /tmp/some-forest)
so tests never touch the user's real ~/forest.
When you need to detach and reattach
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 · 209 lines · 0 tokens per session scan C 1d4b16d9619d
test-forestui is a skill published in the GitHub repository flipbit03/forestui (26 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,152 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
ptywright-testing
Build, run, record, replay, debug, and maintain deterministic terminal, TUI, PTY cassette, and browser-terminal agent regression tests with ptywright. Use when an agent needs to drive CLI/TUI apps, create ptywright scripts, configure ptywright.config., record or replay PTY output, solidify browser terminal agent flows…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…