impact-statusline

impact-statusline is a command for Claude Code from fallow-rs/fallow-skills. It costs 13 tokens per session (529 once invoked), scanned A, original, MIT.

A command for viewing or managing the compact Fallow Impact status display in Claude Code.

In plain words
What is it for?
Use it to check, set up, compose, or remove the Fallow Impact statusline at user or project scope.
Why use it?
It lets you inspect the current statusline and choose whether to add, combine, or remove it without changing settings unexpectedly.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the fallow plugin — 2 skills, 1 command shipped together

Good fit Use it to check, set up, compose, or remove the Fallow Impact statusline at user or project scope.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add fallow-rs/fallow-skills
Claude Code
/plugin install fallow

Made for: Claude Code.

Or install fallow, the plugin that ships this one along with the rest of its 2 skills, 1 command.

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 impact-statusline

README.md
[![agentmods](https://agentmods.dev/badge/commands/fallow-rs/fallow-skills/impact-statusline/github.svg)](https://agentmods.dev/commands/fallow-rs/fallow-skills/impact-statusline)
Your own site
<a href="https://agentmods.dev/commands/fallow-rs/fallow-skills/impact-statusline"><img src="https://agentmods.dev/badge/commands/fallow-rs/fallow-skills/impact-statusline/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 impact-statusline

Your own site · 80×15
<a href="https://agentmods.dev/commands/fallow-rs/fallow-skills/impact-statusline"><img src="https://agentmods.dev/badge/commands/fallow-rs/fallow-skills/impact-statusline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 529 The whole file, excluding the scripts and references it only reads on demand.
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.00013 $0.00529
Opus 5 $0.00006 $0.00264
Sonnet 5 $0.00003 $0.00106
Haiku 4.5 $0.00001 $0.00053

Measured 3d ago against content hash 010da563e573, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

impact-statusline 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 3d 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.

fallow/commands/impact-statusline.md · 61 lines

What it actually says

Fallow Impact statusline

Arguments: $ARGUMENTS

Manage Fallow's branded, compact Impact segment for Claude Code. Never enable Impact on the user's behalf.

Parse the request

  • Action: status, setup, or remove. Default to status.
  • Scope: user or project. Default to user.
  • Mode for setup: replace or compose.
  • project means the private, gitignored .claude/settings.local.json in ${CLAUDE_PROJECT_DIR}. Never edit the shared .claude/settings.json.

Command forms:

node "${CLAUDE_PLUGIN_ROOT}/bin/fallow-impact-statusline.mjs" inspect --scope user --root "${CLAUDE_PROJECT_DIR}"
node "${CLAUDE_PLUGIN_ROOT}/bin/fallow-impact-statusline.mjs" install --scope user --root "${CLAUDE_PROJECT_DIR}" --mode compose --confirm
node "${CLAUDE_PLUGIN_ROOT}/bin/fallow-impact-statusline.mjs" remove --scope user --root "${CLAUDE_PROJECT_DIR}" --confirm

Status

Run inspect and report:

  • the exact preview;
  • whether a statusline already exists;
  • whether Fallow already manages it;
  • the settings scope and path.

Do not modify files.

Setup

  1. Run inspect first and show the exact preview.
  2. If no statusline exists, use replace.
  3. If a command-based statusline exists and no mode was supplied, ask whether to compose with it or replace it. Recommend compose.
  4. If a non-command statusline exists and no mode was supplied, explain that it cannot be composed and ask whether to replace it.
  5. Only after that decision, run install with --mode <mode> --confirm.
  6. Report the settings path and tell the user the statusline appears on the next Claude interaction.

If the preview says fallow impact off, tell the user they may run fallow impact enable themselves. Do not run it.

Remove

Run remove --confirm and report the result. When the helper refuses because the statusline changed after Fallow setup, tell the user and do not overwrite their configuration by hand.

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. 3d ago Changed · -13 lines 010da563e573
  2. 10d ago First seen · 74 lines · 13 tokens per session scan A 5f56966e2254

Subscribe to this mod's changes

impact-statusline is a command published in the GitHub repository fallow-rs/fallow-skills (121 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 529 once invoked, about $0.0001 per session on Opus 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.