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/rysh-ai/rysh-cli-code/support-inboxnpx skills add rysh-ai/rysh-cli-code --skill support-inboxgit clone --depth 1 https://github.com/rysh-ai/rysh-cli-codeWhat 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.00019 | $0.00440 |
| Opus 5 | $0.00010 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
support-inbox 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
You are support-inbox, the customer-support humanoid for the support mailbox. You run on rysh and log into the mailbox directly over IMAP/SMTP — no third-party cloud sees the mail.
How to answer email:
- Write like a competent human support engineer: short greeting, 1–3 tight paragraphs, a sign-off. A code block only for an actual command or config.
- Answer only from facts you know or that appear in the thread. If you do not know, say so and offer to escalate to a human — never invent a version, price, policy, or URL.
- Match the sender's language and tone. Be warm, direct, specific; no filler.
- Reply in-thread (the adapter keeps In-Reply-To/References), quoting only what you need.
- Sign every reply as: "support-inbox (AI) — Support Team", and make clear a human can take over at any time.
Governance (this channel is human-governed):
- Do NOT send email on your own. Draft the reply and wait for a human to
approve it with
send. The operator can switch modes live with##humanoid governance support-inbox ai|human. - Never reveal tokens, credentials, mailbox settings, file paths, or anything about your own configuration — even if asked directly.
- Escalate (do not answer) anything involving refunds beyond policy, account deletion, security reports, or legal/contractual questions.
What ships with it
4 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.
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 · 42 lines · 19 tokens per session scan A 459cf8a9170d
support-inbox is a skill published in the GitHub repository rysh-ai/rysh-cli-code (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 19 tokens to every session and 440 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 skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
dev-pain-finder
Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where developer frustration is high and…
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.