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/chinkan/rustfox/coding-assistantnpx skills add chinkan/RustFox --skill coding-assistantgit clone --depth 1 https://github.com/chinkan/RustFoxWhat 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.00013 | $0.00200 |
| Opus 5 | $0.00006 | $0.00100 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
coding-assistant 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
Coding Assistant
When the user asks for help with code:
- Understand first — Ask clarifying questions if the request is ambiguous
- Read before writing — Use read_file to understand existing code before modifying
- Small changes — Make focused, minimal changes. Don't refactor unrelated code
- Explain your reasoning — Briefly explain what you changed and why
- Test awareness — Suggest how to test the changes if applicable
When reviewing code:
- Point out bugs, security issues, and performance problems
- Suggest improvements but don't over-engineer
- Be specific — reference line numbers and provide fixed code
When debugging:
- Ask for error messages and reproduction steps
- Use execute_command to investigate (check logs, run tests)
- Explain the root cause, not just the fix
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 · 26 lines · 13 tokens per session scan A c9e672710ec9
coding-assistant is a skill published in the GitHub repository chinkan/RustFox (6 stars, last pushed 26d ago), licensed MIT. It adds 13 tokens to every session and 200 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
glm-master-skill
Documentation-only master skill for GLM ecosystem discovery and installation. This skill does not execute scripts or subprocess commands. It provides a curated list of official GLM skills, install methods, and source links.
wrongstack-mailbox
Use this skill when the user wants to communicate with WrongStack's shared project mailbox from outside WrongStack — read messages sent by WrongStack agents, send replies, broadcast to all, or stay visible as an online agent. Triggers: user says "check the WrongStack mailbox", "send to WrongStack", "wrongstack mail"…
mailbox-bridge
Use this skill when external coding agents (Claude Code, Aider, custom scripts) need to participate in the project's shared WrongStack mailbox, or when a user asks to "expose the mailbox", "let Claude Code read the mailbox", "external agent mailbox", "mailbox bridge", or "HTTP mailbox bridge". Starts a loopback HTTP…
shadow-agent
Use this skill when you need a background monitoring agent that watches the fleet, detects anomalies, and can intervene on command. Triggers: user says "shadow", "monitoring agent", "fleet watcher", "hoop command", "spike detection".
auto-review
Use this skill to configure and understand the built-in auto-review plugin (wstack-auto-review) that fires automated code review subagents on every code change during a session. Triggers: user says "auto review", "otomatik review", "auto code review", "her değişiklikte review", "/auto-review".
code-agent
General-purpose coding agent that reads, writes, and edits code, and searches codebases.