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.
/plugin marketplace add arpan1221/claude-effort-router/plugin install effort-routerWrote 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/arpan1221/claude-effort-router/effort-router-setup)<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.
<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>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 | $0.00032 | $0.00418 |
| Sonnet 5 | $0.00013 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00084 |
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 9d 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 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.shto~/.claude/hooks/(a stable path, so updating or removing the plugin cannot leave a dangling statusline command). - Sets
statusLine.commandin~/.claude/settings.jsonto 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 including5h/7dusage. - Backs settings up to
settings.json.bak-effort-routerand validates the generated JSON, aborting rather than writing a broken file.
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.
- 9d ago First seen · 84 lines · 65 tokens per session scan B a09b5cb80878
effort-router-setup is a skill published in the GitHub repository arpan1221/claude-effort-router (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 836 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…