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 agentmods add commands/aneja5/forge-skills/scalegit clone --depth 1 https://github.com/aneja5/forge-skillsWhat 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 | $0.00017 | $0.00158 |
| Opus 5 | $0.00009 | $0.00079 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
scale 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 2d 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.
What it actually says
Invoke the forge-skills:scalability-analysis skill.
Read .forge/architecture.md. If it doesn't exist, tell the user to run /architect first.
Document current capacity per component. Define scale targets with the user (10x, 100x, 1000x). Identify bottlenecks per component at each target — what breaks first and at what threshold. Calculate scale-out triggers with specific metrics and thresholds. Project costs at each milestone with real pricing. Map migration decision points (when to add caching, shard, split monolith). Define data lifecycle policies for every data store.
After writing: "Scalability analysis written to .forge/scalability.md."
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.
- 2d ago First seen · 18 lines · 17 tokens per session scan A 6ab0b4332ef2
scale is a command published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 158 once invoked, about $0.0001 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.
Other commands, from other repositories
index
Command "index" from cesarandreslopez/tauri-agent-tools, covering command reference, command summary, categories, visual capture and dom inspection.
console-monitor
Monitor console output (log/warn/error/info/debug) in real-time.
eval
Evaluate a JavaScript expression in the Tauri app's webview.
info
Show window geometry and display server info.
list-windows
List all visible windows, marking Tauri apps.
git
Unified git operations - commits, pull requests, and issue management.