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 sonichi/sutando --skill trusted-capabilitiesgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/trusted-capabilities)<a href="https://agentmods.dev/skills/sonichi/sutando/trusted-capabilities"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/trusted-capabilities/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sonichi/sutando/trusted-capabilities"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/trusted-capabilities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00441 |
| Opus 5 | $0.00013 | $0.00220 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
trusted-capabilities 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 5d 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
Trusted capabilities
Use this skill when the owner asks to find, assess, install, or update reusable agent skills and tools from public ecosystems.
The catalog is allowlist-only. Skill sources can be installed after inspection. Tool sources can be discovered and statically inspected, while tool and index sources remain install-disabled because their setup and runtime permissions are project-specific.
C=skills/trusted-capabilities/scripts/catalog.py
python3 "$C" sources
python3 "$C" search browser
python3 "$C" inspect openai-skills skills/.curated/browser-automation
python3 "$C" inspect mcp-reference-servers src/filesystem
python3 "$C" install openai-skills skills/.curated/browser-automation
# Review the dry-run output, then copy its exact commit into the write:
python3 "$C" install openai-skills skills/.curated/browser-automation --commit <40-char-sha> --yes
python3 "$C" update browser-automation
python3 "$C" update browser-automation --commit <40-char-sha> --yes
install and update show the resolved commit, destination, and risk findings,
then print a write command pinned to that immutable commit. Writes require both
the full --commit <sha> from the reviewed dry run and --yes; resolving the
moving default branch again is not authorization to write. Updates also
re-check that the source remains installable in the current allowlist. The
default destination is the runtime's canonical $CLAUDE_CONFIG_DIR/skills/
path via src/util_paths.py. Use --dest-root for an explicit test or
alternate install root.
Every install is pinned to a Git commit, fetched file-by-file, bounded by file
count and total size, and written atomically. Provenance is recorded in
.sutando-source.json; update uses it to compare and fetch the same upstream
path.
What ships with it
2 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.
- 5d ago First seen · 42 lines · 25 tokens per session scan A 582aa5628845
trusted-capabilities is a skill published in the GitHub repository sonichi/sutando (394 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 441 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
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.