forge-router

forge-router is a skill for Claude Code from ForgeyClap/claude-forge. It costs 42 tokens per session (10,888 once invoked), scanned A, original, MIT.

A Forge task router that classifies a request by project area and difficulty, then chooses the smallest suitable team of agents. It also checks available project guidance and tools before routing the work.

In plain words
What is it for?
Use it at the start of Forge work involving websites, mobile apps, automation, integrations, scraping, dashboards, or other supported project types.
Why use it?
It prevents unsuitable or unnecessarily large teams from being used and makes the project’s existing rules part of the decision.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is node .claude/forge-dashboard/log-event.cjs <run_id> agent_work_package_created \.

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code.

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 forge-router

README.md
[![agentmods](https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-router.svg)](https://agentmods.dev/skills/forgeyclap/claude-forge/forge-router)
Your own site
<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-router"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-router.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,888 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00042 $0.10888
Opus 5 $0.00021 $0.05444
Sonnet 5 $0.00008 $0.02178
Haiku 4.5 $0.00004 $0.01089

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

Security

Grade A, and why

forge-router 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 5d 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.

.claude/skills/forge-router/SKILL.md · 248 lines

How it starts

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

Forge router (agent selection)

Self-improvement substrate (wp-skill-evals, 2026-07-31): before applying this skill, read learnings.md in this skill's own folder and honor its corrections. After a run that produced a genuine correction (an owner fix, a false assumption caught, a preference stated), append it to learnings.md with a date and real evidence — never invent a lesson that didn't happen.

You are the router. You do not implement. You output a TEAM PLAN + Project Adaptation block, then hand off to the matching domain playbook. Use the smallest team that fits — never spawn an agent per trivial step.

Step 0 — Read project memory + ECC inventory first (required)

Before routing, read (if present): .claude/FORGE_PROJECT_PROFILE.md, .claude/FORGE_MEMORY.md, .claude/FORGE_TASK_HISTORY.md, .claude/FORGE_ECC_MODE.json. Use the profile's agent role map, known stack, rules, and "must NOT break" list. Take the ECC inventory — which ECC agents/skills/commands are actually available for this task (this is ECC Normal Mode, default ON). If no profile exists, infer one from the files and create it. Never fake project knowledge or ECC availability — mark inferred/unknown.

Step 0-owner — Owner Prefs, Standing Rules & Autonomy (required, before intake) — WAVE B / B4

Read the owner-governance stack in config/orchestration/precedence.md order (hard-gates > current owner instruction > standing-rules > owner-profile defaults > auto-defaults — never re-derive this ordering here, that file is the single source of truth): (1) forge-bin/forge-prefs.cjs::resolve()/list() — the owner-profile defaults (.claude/FORGE_OWNER_PROFILE.json + the owner-write-only global copy + an optional env override; merge order project < global < env); (2) forge-bin/forge-standing.cjs::match({type, paths}) — the active, evidence-backed standing rules for this run (advisory, injected into dispatch prompts as ADVISORY OWNER CONSTRAINTS, never a silent block); (3) forge-bin/forge-autonomy.cjs::decide() — which continue-within-mission mode applies, always deferring to the live hard-gate classifier first. Then compose and log the applied-prefs ECHOnode .claude/forge-bin/forge-echo.cjs emit <run_id> (or the module API forge-echo.cjs::emitEcho()) — a single owner_prefs_loaded event summarizing which prefs/rules actually applied, so precedence.md's ordering is VISIBLE on the dashboard/run log, not merely documented. Re-run forge-echo.cjs compose --type <domain> after Step 1's domain classification below if a domain-scoped standing rule should be re-checked with the now-known type. Never fabricate a pref/rule — an unresolved layer degrades honestly (see forge-prefs.cjs's per-layer notes); nothing here promotes a staged FORGE_PREF_CANDIDATES.json entry to active — that requires a real owner /forge remember (forge-standing.cjs::remember()).

Read the full file on GitHub · 248 lines

Files

What ships with it

3 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.

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. 5d ago First seen · 248 lines · 42 tokens per session scan A d12c1bec0b50

Subscribe to this mod's changes

forge-router is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 10,888 once invoked, about $0.0002 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-31.