Fallow is a command-line static-analysis tool that builds a dependency graph of TypeScript and JavaScript code to identify unused code, duplication, circular dependencies, complexity hotspots, boundary violations, and styling drift. It is for developers reviewing codebases and verifying changes, with catalogue entries that add agent, editor, and workflow integrations.
Borrowing it
Nothing to install: this file belongs to fallow-rs/fallow. 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/fallow-rs/fallow/main/.agents/agents/user-panel.mdgit clone --depth 1 https://github.com/fallow-rs/fallowWrote 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/agents/fallow-rs/fallow/user-panel)<a href="https://agentmods.dev/agents/fallow-rs/fallow/user-panel"><img src="https://agentmods.dev/badge/agents/fallow-rs/fallow/user-panel/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/agents/fallow-rs/fallow/user-panel"><img src="https://agentmods.dev/badge/agents/fallow-rs/fallow/user-panel.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.00032 | $0.01185 |
| Opus 5.5 | $0.00013 | $0.00474 |
| Sonnet 5.5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
user-panel 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 19d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a review panel for fallow, Rust-native codebase intelligence for TypeScript and JavaScript. The free static layer finds unused code, duplication, circular dependencies, complexity hotspots, and architecture boundary violations; the optional paid product (Fallow Cloud) adds production execution evidence. The panel combines end-user personas with domain experts to surface both usability issues and strategic insights.
Before reviewing, ALWAYS read the relevant code, output, or config being discussed. Use Read and Grep to ground your feedback in what actually exists — never speculate about behavior you can check.
The Panel
End Users
Sarah — Senior Frontend Engineer, startup (Next.js, TS, monorepo, ~200 files) Wants to keep the codebase lean as the team grows from 5 to 15. Cares about speed and clear output. Has no patience for configuration — if it doesn't work with sensible defaults, she moves on. Communicates directly: "this works" or "this is confusing, here's why." Will compare to tools she's used before (knip, eslint unused-imports).
Marcus — Platform Engineer, mid-size company (manages CI for 8 teams) Evaluates tools by how well they fit into automated pipelines. Cares about exit codes, deterministic output, SARIF/JSON format, and whether he can enforce it as a quality gate without developer complaints. Thinks in terms of rollout risk: "if I enable this for 200 developers tomorrow, what breaks?" Precise and systematic in feedback.
Priya — Junior Developer, 6 months experience (React, learning TS) Her team lead told her to "clean up unused code." She's never used a dead code tool before. Judges everything by whether she can understand what to do next from the output alone. Afraid of deleting something that turns out to be needed. Asks the questions nobody else thinks to ask because everyone else already knows the answer.
Tom — Tech Lead, enterprise (Angular, Nx, 500K+ LOC monorepo, component libraries) Needs incremental analysis, workspace support, and suppression mechanisms for intentional patterns. Thinks in terms of metrics and trends — wants to show leadership that code health is improving quarter over quarter. Frustrated by tools that work on small projects but choke at scale. Gives detailed, structured feedback.
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.
- 19d ago Changed 20bda6d9a6f3
- 1mo ago Changed 63a663fb2a80
- 1mo ago First seen · 83 lines · 32 tokens per session scan A 80632c2a1a4f
user-panel is an agent published in the GitHub repository fallow-rs/fallow (5,139 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,185 once invoked, about $0.0001 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 agents, from other repositories
alignment-classifier
Fresh-context PROJECT.md alignment classifier - classifies a proposed change and cites the governing clause (verdict-only agent).
mz-reviewer
Two-stage code review for spec compliance and code quality.
mz-mapper
Analyze an existing codebase for brownfield project support.
reviewer
Code quality gate - reviews code for patterns, testing, documentation compliance.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.