Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/commands/fmarzochi/egc/model-route)<a href="https://agentmods.dev/commands/fmarzochi/egc/model-route"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/model-route/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/commands/fmarzochi/egc/model-route"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/model-route.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.00000 | $0.00143 |
| Opus 5.5 | $0.00000 | $0.00057 |
| Sonnet 5.5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
model-route 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.
This is a copy
97% identical to model-route — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Model Route Command
Recommend the best model tier for the current task by complexity and budget.
Usage
/model-route [task-description] [--budget low|med|high]
Routing Heuristic
haiku: deterministic, low-risk mechanical changessonnet: default for implementation and refactorsgemini-2.5-pro: architecture, deep review, ambiguous requirements
Required Output
- recommended model
- confidence level
- why this model fits
- fallback model if first attempt fails
Arguments
$ARGUMENTS:
[task-description]optional free-text--budget low|med|highoptional
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 First seen · 27 lines · 0 tokens per session scan A f08cc2a5e304
model-route is a command published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 143 tokens. A static security scan graded it A with 0 findings. It is 97% identical to model-route, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
demand-discovery
Run automated niche demand discovery research across 7 data sources and 26 categories.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
handoff
Export a Waybill Bundle by default, or import one when requested.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
t800-onboard
A command for newcomers that explains what is installed in Cursor globally and in the current project, plus what the T-800 team can do.
checklist
Generate a custom checklist for the current feature based on user requirements.