claude-plugins-community is a read-only mirror of a marketplace listing community-contributed plugins for Claude Cowork and Claude Code. It is for discovering and installing plugins that extend those Claude products, while submissions are handled through Anthropic’s separate review process. Catalogue add-ons represent plugins, skills, and integrations associated with this marketplace.
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 anthropics/claude-plugins-community --skill tres-onboardinggit clone --depth 1 https://github.com/anthropics/claude-plugins-communityWrote 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/anthropics/claude-plugins-community/tres-onboarding)<a href="https://agentmods.dev/skills/anthropics/claude-plugins-community/tres-onboarding"><img src="https://agentmods.dev/badge/skills/anthropics/claude-plugins-community/tres-onboarding/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/anthropics/claude-plugins-community/tres-onboarding"><img src="https://agentmods.dev/badge/skills/anthropics/claude-plugins-community/tres-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 42 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00202 | $0.02008 |
| Opus 5 | $0.00101 | $0.01004 |
| Sonnet 5 | $0.00040 | $0.00402 |
| Haiku 4.5 | $0.00020 | $0.00201 |
Grade A, and why
tres-onboarding 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 9d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRES Finance — Full Entity Onboarding
Orchestrate the complete onboarding of a new entity/customer/account into TRES Finance. This skill does not contain its own low-level logic — instead, it drives the user through 8 sequential steps, invoking the dedicated skill for each one. Think of it as a conductor that keeps the onboarding moving forward while each sub-skill handles the details.
Before You Start
No visualizations for input gathering. Do NOT use show_widget, HTML widgets, interactive forms, AskUserQuestion widgets, or any visualization tool when collecting initial context from the user or presenting the onboarding roadmap. Ask all questions and present the roadmap as plain text in the chat. This keeps the flow fast and responsive — building a widget just to ask for a name and wallet list adds unnecessary latency. Visualizations are fine later when individual sub-skills need them (e.g., balance validation dashboards, recon gap tables), but the onboarding kick-off and step transitions must be text-only.
-
Confirm intent. The user must have explicitly requested a full onboarding (new entity, new customer, new account). If the request is ambiguous, ask: "Are you looking to run the full onboarding flow for a new entity, or do you just need help with a specific step (like uploading wallets or validating balances)?"
-
Collect context. Ask the user in plain text (no widgets, no forms) for:
- The entity/customer/account name
- Any wallets or exchange accounts they already have ready (file, list, etc.)
- Whether they have a target date in mind for the onboarding
-
Present the roadmap. Before diving in, show the user the roadmap as plain text in the chat (not as an HTML widget or visualization) so they know what to expect. Use something like:
Here's the onboarding roadmap for [Entity Name]:
- Upload Wallets — Add on-chain wallets and/or exchange accounts
- Data Collection (Commit) — Pull on-chain data for the uploaded wallets
- Validate Balances — Cross-check TRES balances against on-chain sources
- Reconciliation — Review and resolve any balance gaps
- Cost Basis — Configure and run cost basis calculation
- Export Unidentified Addresses — Extract 3rd-party addresses from transactions
- Import Contacts — Label and import the identified addresses back into TRES
- Rollup Rules — Set up transaction aggregation for high-volume wallets
We'll go through each step together. Ready to start?
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.
- 9d ago First seen · 208 lines · 202 tokens per session scan A 507658702b7e
tres-onboarding is a skill published in the GitHub repository anthropics/claude-plugins-community (3,605 stars, last pushed 14d ago), licensed Apache-2.0. It adds 202 tokens to every session and 2,008 once invoked, about $0.0010 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
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.