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 chinkan/RustFox --skill sup-opsgit clone --depth 1 https://github.com/chinkan/RustFoxWrote 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/chinkan/rustfox/sup-ops)<a href="https://agentmods.dev/skills/chinkan/rustfox/sup-ops"><img src="https://agentmods.dev/badge/skills/chinkan/rustfox/sup-ops.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.00022 | $0.00172 |
| Opus 5 | $0.00011 | $0.00086 |
| Sonnet 5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
sup-ops 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 4d 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
When to use
When a task asks to run a script, automate a system action, or perform shell-based ops.
Operating rules
- State expected effects in plain language before running anything destructive.
- Prefer a dry-run or read-only check first when available.
- Run inside the configured sandbox directory; never escape it.
- Capture command output and exit codes as evidence.
- Roll back or document recovery steps for any failure.
Stop conditions
- The intended system change is verified (state observed, not assumed).
- All commands and their outputs are recorded.
- No unintended side effects remain.
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.
- 4d ago First seen · 22 lines · 22 tokens per session scan A 8a1e708e9456
sup-ops is a skill published in the GitHub repository chinkan/RustFox (7 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 172 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-09-03.
Other skills, from other repositories
Vector Databases
Guides retrieval-store design, indexing, and query behavior for embedding-backed systems without confusing storage with application truth.
esm
Comprehensive toolkit for protein language models including ESM3 (generative multimodal protein design across sequence, structure, and function) and ESM C (efficient protein embeddings and representations). Use this skill when working with protein sequences, structures, or function prediction; designing novel…
agentfield-use
Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
parse-document
Convert a PDF, scan, image of a page, or office file to clean markdown through the connected Superlinked MCP edge, so the source document is not read into model context directly. Use when the user asks to read, parse, OCR, extract from, summarize, or answer questions about a document.
agent-evaluation
Run one specified Test Agent on one specified Benchmark Case exactly once, privately score that execution, and return one protocol result.