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 skills/sopaco/cowork-forge/rtk-skillnpx skills add sopaco/cowork-forge --skill rtk-skillgit clone --depth 1 https://github.com/sopaco/cowork-forgeWrote 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/sopaco/cowork-forge/rtk-skill)<a href="https://agentmods.dev/skills/sopaco/cowork-forge/rtk-skill"><img src="https://agentmods.dev/badge/skills/sopaco/cowork-forge/rtk-skill.svg" alt="Measured on agentmods" 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.00053 | $0.01760 |
| Opus 5 | $0.00026 | $0.00880 |
| Sonnet 5 | $0.00011 | $0.00352 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade A, and why
rtk-skill 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 6d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RTK Skill (Rust Token Killer)
RTK is a CLI proxy that filters and compresses command output before it reaches the LLM (typically 60–90% token savings).
Resolve the RTK command (read first)
Use conventional paths only — never machine-specific absolute paths like /Users/... or C:\Users\....
On Windows, tools deploy to %USERPROFILE%\.terrain\bin\ (also written as ~/.terrain/bin/ in Git Bash / PowerShell 7+). Binaries use .exe extensions; PATHEXT resolves rtk → rtk.exe.
| Priority | Command prefix | When |
|---|---|---|
| 1 | ~/.terrain/bin/rtk |
Terrain env integration or desktop app (see existence check below) |
| 2 | bunx @terrain-ai/rtk |
No Terrain install; needs network once |
| 3 | npx @terrain-ai/rtk |
Same as bunx if Bun unavailable |
Optional manifest (local, gitignored): .terrain/env/agent-tools.json — same ~/.terrain/bin/… conventions.
Existence check (cross-platform):
| Shell | Check |
|---|---|
| bash / zsh / Git Bash | [ -x ~/.terrain/bin/rtk ] || [ -x ~/.terrain/bin/rtk.exe ] |
| PowerShell | Test-Path "$HOME\.terrain\bin\rtk.exe" |
| cmd | if exist "%USERPROFILE%\.terrain\bin\rtk.exe" |
Shell rules:
- Invoke as
~/.terrain/bin/rtk <cmd>— tilde expands at word start in bash/zsh/Git Bash/PowerShell 7+. - Do not
export RTK="$(jq -r .rtk …)"then"$RTK"— quoted variables do not expand~. - Do not assume bare
rtkis on PATH.
Example (pick one prefix per session after the existence check):
# bash / Git Bash
if [ -x ~/.terrain/bin/rtk ] || [ -x ~/.terrain/bin/rtk.exe ]; then
PREFIX=~/.terrain/bin/rtk
else
PREFIX="bunx @terrain-ai/rtk"
fi
$PREFIX git status
# PowerShell
$PREFIX = if (Test-Path "$HOME\.terrain\bin\rtk.exe") { "$HOME\.terrain\bin\rtk.exe" } else { "bunx @terrain-ai/rtk" }
& $PREFIX git status
Verify:
~/.terrain/bin/rtk gain || bunx @terrain-ai/rtk gain
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.
- 6d ago First seen · 214 lines · 53 tokens per session scan A df03475370c1
rtk-skill is a skill published in the GitHub repository sopaco/cowork-forge (92 stars, last pushed 11d ago), licensed MIT. It adds 53 tokens to every session and 1,760 once invoked, about $0.0003 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-30.
Other skills, from other repositories
skill
Manage local skills - list, add, remove, search, edit, setup wizard.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
hud
Configure HUD display options (layout, presets, display elements).
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
cmux-keyboard-shortcuts
Guide and apply cmux keyboard shortcut customization. Use when the user asks to customize, rebind, unbind, reset, audit, or create shortcut templates for cmux, including tmux-style, Vim-style, terminal-first, browser-heavy, iTerm/Terminal-like, or agent-triage layouts.