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.
npx skills add jamesdsizemore/rush-cli --skill rushgit clone --depth 1 https://github.com/jamesdsizemore/rush-cliWrote 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/jamesdsizemore/rush-cli/rush)<a href="https://agentmods.dev/skills/jamesdsizemore/rush-cli/rush"><img src="https://agentmods.dev/badge/skills/jamesdsizemore/rush-cli/rush/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/jamesdsizemore/rush-cli/rush"><img src="https://agentmods.dev/badge/skills/jamesdsizemore/rush-cli/rush.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.00073 | $0.02006 |
| Opus 5.5 | $0.00029 | $0.00802 |
| Sonnet 5.5 | $0.00015 | $0.00401 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
rush 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rush
Rush is a local code-quality toolbelt. It runs installed engines (linters,
type checkers, test runners, security scanners) and returns one structured
result per call: {status, findings, summary, raw}.
Triggers
Call Rush:
- Before every commit: run
rush_checkon the project and fix or report everyfailandwarnbefore committing. - After every code change: run
rush_check, orrush_linton the changed files, before saying the change is done. - When the user asks about code quality, lint, formatting, types, tests, security, secrets or dead code: run the matching Rush tool instead of guessing.
Profiles
core(new registrations runrush mcp serve --profile core) exposes exactly seven tools:rush_status,rush_check,rush_lint,rush_review,rush_security,rush_test,rush_memory.full(rush mcp serve --profile full, and every older registration without--profile) keeps every existing tool name and alias plusrush_statusandrush_check. The server's own tool list is the full list; read it instead of assuming a tool exists.- A tool that is not in the connected profile fails as an unknown tool. The profile limits which tools are listed; it never grants a permission.
Paths
- Not every tool takes a
path. Read each tool's input schema. - A relative
pathresolves against the declared project root. Declare it withproject(a registered project path) orproject_id. With no declared root, a relative path resolves against the directory the MCP server started in. - Absolute paths keep their identity. Rush never follows a symlink out of the project root.
- Project memory, cache and results live under the resolved project root.
Statuses
| Status | Meaning |
|---|---|
ok |
The requested work ran and found nothing to report. |
warn |
The work ran and found problems, or required work ran only partly. |
fail |
The work ran and found blocking problems. |
error |
Rush or an engine failed to run; the result says why. |
skipped |
No work was performed: the engine is missing, there were no supported targets, or a permission was denied. |
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.
- 3d ago First seen · 188 lines · 73 tokens per session scan A fa48967692cf
rush is a skill published in the GitHub repository jamesdsizemore/rush-cli (0 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 2,006 once invoked, about $0.0003 per session on Opus 5.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-10-15.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.