Borrowing it
Nothing to install: this file belongs to draekien-industries/membank. 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/draekien-industries/membank/main/.agents/skills/fallow/SKILL.mdgit clone --depth 1 https://github.com/draekien-industries/membankWrote 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/draekien-industries/membank/fallow)<a href="https://agentmods.dev/skills/draekien-industries/membank/fallow"><img src="https://agentmods.dev/badge/skills/draekien-industries/membank/fallow/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/draekien-industries/membank/fallow"><img src="https://agentmods.dev/badge/skills/draekien-industries/membank/fallow.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.00114 | $0.12732 |
| Opus 5 | $0.00057 | $0.06366 |
| Sonnet 5 | $0.00023 | $0.02546 |
| Haiku 4.5 | $0.00011 | $0.01273 |
Grade C, and why
fallow scanned grade C with 2 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
| `health` | Function complexity analysis (also covers component templates as synthetic `<template>` findings: Angular external `.html` files via `templateUrl` AND inline `@Component({ template: \`...\` })` literals, plu Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| `boundary-violation` | `--boundary-violations` | - | `// fallow-ignore-next-line boundary-violation` | Imports crossing architecture zone boundaries. Presets: `layered`, `hexagonal`, `feature-sliced`, `bulletproof`; `a This is a copy
97% identical to fallow — 130 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fallow: codebase intelligence for TypeScript and JavaScript
Codebase intelligence for TypeScript and JavaScript. The static layer analyzes code and styles and reports quality, changed-code risk, cleanup opportunities, circular dependencies, code duplication, complexity hotspots, architecture boundary violations, design-system styling drift, feature flag patterns, and opt-in security candidates. Runtime coverage merges production execution data into the same fallow health report for hot-path review, cold-path deletion confidence, and stale-flag evidence, with a single local capture available by default and continuous/cloud runtime monitoring available as an optional mode. Broad framework plugin coverage, zero configuration, sub-second static analysis.
When to Use
- Find cleanup opportunities: unused files, exports, types, members, dependencies, or stale flags.
- Detect code duplication, circular dependencies, architecture boundary issues, and complexity hotspots.
- Find functions that may implement the same intent despite different names, syntax, or control flow (
fallow similar-code). - Check styling consistency, CSS dead surface, and design-token drift.
- Audit changed code before a commit, PR, release, or refactor.
- Set up CI quality gates, duplication thresholds, and regression baselines.
- Auto-fix supported unused exports and dependencies after
--dry-run. - Investigate why a specific export, dependency, file, or issue type was reported.
- Surface local security candidates for an agent to verify (
fallow security). - Find untested but runtime-reachable code (
fallow health --coverage-gaps). - Rank complexity hotspots, owners, and refactoring targets (
fallow health --hotspots --ownership --targets). - Review what fallow has surfaced over time (
fallow impact). - Confirm exact TypeScript symbol use, affected tests, API leaks, or public type coupling when syntactic evidence is insufficient (
--type-aware).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 499 lines · 114 tokens per session scan C 4dba0d924dd3
fallow is a skill published in the GitHub repository draekien-industries/membank (2 stars, last pushed 3d ago), licensed MIT. It adds 114 tokens to every session and 12,732 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, runs shell commands). It is 97% identical to fallow, differing in 130 lines, and is treated as a copy.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.