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/skills/triage-issue/SKILL.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/skills/fallow-rs/fallow/triage-issue)<a href="https://agentmods.dev/skills/fallow-rs/fallow/triage-issue"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/triage-issue/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/fallow-rs/fallow/triage-issue"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/triage-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00299 |
| Opus 5.5 | $0.00021 | $0.00120 |
| Sonnet 5.5 | $0.00011 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
triage-issue 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.
What it actually says
Triage Issue
Use the GitHub connector and local repo inspection together.
Workflow:
- Fetch the issue and comments.
- Reproduce the report on a binary built from current
mainbefore you judge it. A report against an older release can be fixed already. - Inspect the relevant code paths locally.
- Determine whether the issue is valid, overstated, underspecified, or already covered.
- Recommend priority and whether the issue should be kept, split, narrowed, or closed.
- Give acceptance criteria tied to the current codebase.
Give each claim about cause or history one confidence level:
- direct: you ran it, or the source shows it;
- supported: two independent sources agree;
- inferred: it follows from the evidence, but nothing shows it;
- speculative: plausible, with no evidence;
- unknown.
Write "because" only with a source: a file:line, a commit, or command
output. Code does not prove the intent of its author.
When useful, pull in:
rust-reviewpanel-reviewteam-assembly
Always cite local file references for implementation claims.
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 Changed · +12 lines 3a5106365697
- 2mo ago First seen · 23 lines · 53 tokens per session scan A 045a474ffeb0
triage-issue is a skill published in the GitHub repository fallow-rs/fallow (5,273 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 299 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
argot-refresh
Refresh Argot's committed fit snapshot safely — first diagnose why maintenance is recommended, re-audit corpus scope and structural path changes, review stale mutes and policy entries with the user, then fit locally, verify, and prepare the reviewed .argot/ update. Use when argot status, argot check, MCP, or CI…
cli-audit-code
Audit code quality with weighted scoring across 12 dimensions (naming, complexity, module design, DRY, errors, security, tests, architecture). Detects named anti-patterns (Fowler/Mantyla taxonomy). Use when reviewing code quality, auditing clean code compliance, checking for code smells, or saying 'audit code', 'code…
safe-fix-mcp
Finds real dead code (unused imports, functions, classes) and unused dependencies in a Python repository, and proposes a safe, test-gated branch+PR to remove the safely-removable ones. Use this whenever the user asks to find or clean up dead code, unused imports, unused dependencies, or "bloat" in a Python project…
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.