What is effort-router-setup?

A setup tool for connecting effort-router to Claude Code's statusline so it can read actual subscription usage limits. The statusline is the information Claude Code displays about the current session.

Use it to check whether the connection is active, preview the settings change, install the bridge after confirmation, or remove and troubleshoot it.

By itself, effort-router can estimate usage from local transcripts, but those estimates may be inaccurate. This setup adds the missing connection to the real five-hour and seven-day limits.

effort-router-setup — Skill for Claude Code by arpan1221

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 arpan1221/claude-effort-router

Claude Code

/plugin install effort-router

Made for: Claude Code.

Or install effort-router, the plugin that ships this one along with the rest of its 1 skill, 2 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/arpan1221/claude-effort-router/effort-router-setup/github.svg)](https://agentmods.dev/skills/arpan1221/claude-effort-router/effort-router-setup)

Your own site

<a href="https://agentmods.dev/skills/arpan1221/claude-effort-router/effort-router-setup"><img src="https://agentmods.dev/badge/skills/arpan1221/claude-effort-router/effort-router-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/arpan1221/claude-effort-router/effort-router-setup"><img src="https://agentmods.dev/badge/skills/arpan1221/claude-effort-router/effort-router-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 836 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00065	$0.00836
Opus 5.5	$0.00026	$0.00334
Sonnet 5.5	$0.00013	$0.00167
Haiku 4.5	$0.00006	$0.00084

Measured 2mo ago against content hash a09b5cb80878, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

effort-router-setup scanned grade B 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 2mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

This edits the user's `~/.claude/settings.json`, so never run the real command

plugins/effort-router/skills/effort-router-setup/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Effort router setup

The effort-router hook works the moment the plugin is installed, but by default it can only estimate usage from local transcripts — a rough figure, measured about 2.5x off from the real number on one machine.

Real subscription limits (rate_limits.five_hour / .seven_day) are exposed by Claude Code only in the statusline payload. No hook payload carries them, and a plugin's bundled settings.json supports only the agent and subagentStatusLine keys — not the main statusLine. So the plugin cannot wire this itself. This one-time setup does it.

Check current state

effort-router --report

source: real 5h limit / real 7d limit → already wired, nothing to do.
source: estimated from transcripts → the bridge is not active; offer setup.

If effort-router is not on PATH, use sh "${CLAUDE_PLUGIN_ROOT}/scripts/effort-router.sh" --report.

Wire it

Always show the dry run first and get explicit confirmation before writing. This edits the user's ~/.claude/settings.json, so never run the real command unprompted.

sh "${CLAUDE_PLUGIN_ROOT}/scripts/statusline-setup.sh" --dry-run

Show the user the diff, then on confirmation:

sh "${CLAUDE_PLUGIN_ROOT}/scripts/statusline-setup.sh"

Then tell them to restart Claude Code and re-run effort-router --report. Note that rate_limits only appears after the first API response of a session, so a brand-new session may briefly still say estimated — one prompt fixes it.

What it does to their machine

Be upfront about all of this:

Copies usage-snapshot.sh to ~/.claude/hooks/ (a stable path, so updating or removing the plugin cannot leave a dangling statusline command).
Sets statusLine.command in ~/.claude/settings.json to that wrapper.
Preserves any existing statusline. The previous command is saved to ~/.claude/hooks/inner-statusline; the wrapper pipes identical stdin to it and prints its output verbatim, so their statusline looks unchanged. If they had none, the wrapper renders a small default including 5h / 7d usage.
Backs settings up to settings.json.bak-effort-router and validates the generated JSON, aborting rather than writing a broken file.

Read the full file on GitHub · 84 lines

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.

2mo ago First seen · 84 lines · 65 tokens per session scan B a09b5cb80878

Subscribe to this mod's changes

effort-router-setup is a skill published in the GitHub repository arpan1221/claude-effort-router (2 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 836 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

effort-router-setup next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
effort-router-setuparpan1221/claude-effort-router	Skill	2	3mo ago	MIT	B	65	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code

effort-router-setup