Borrowing it
Nothing to install: this file belongs to RohanAnandPandit/trading212-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RohanAnandPandit/trading212-mcp-server/main/.agents/skills/trading212-api-sync/SKILL.mdgit clone --depth 1 https://github.com/RohanAnandPandit/trading212-mcp-serverWrote 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/rohananandpandit/trading212-mcp-server/trading212-api-sync)<a href="https://agentmods.dev/skills/rohananandpandit/trading212-mcp-server/trading212-api-sync"><img src="https://agentmods.dev/badge/skills/rohananandpandit/trading212-mcp-server/trading212-api-sync/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/rohananandpandit/trading212-mcp-server/trading212-api-sync"><img src="https://agentmods.dev/badge/skills/rohananandpandit/trading212-mcp-server/trading212-api-sync.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.00050 | $0.00400 |
| Opus 5 | $0.00025 | $0.00200 |
| Sonnet 5 | $0.00010 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
trading212-api-sync 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
Trading 212 API sync
Treat https://docs.trading212.com/_bundle/api.yaml as authoritative and
docs/api.json as its reviewable snapshot. A passing test suite against the
snapshot does not establish current upstream compatibility.
Workflow
-
From the repository root, run:
uv run --with PyYAML python .agents/skills/trading212-api-sync/scripts/sync_api_schema.py --check -
If drift exists, inspect the reported paths, then refresh the snapshot with
--update. Review the Git diff before changing implementation code. -
Reconcile every relevant change across endpoint paths and methods, authentication, parameters, defaults and limits, request bodies, response fields, enums, pagination, deprecations, tests, and user documentation.
-
Keep request validation strong where it reflects documented or necessary trading safety, but do not invent format restrictions such as undocumented ticker character sets. Response models must tolerate additive fields, and changed upstream enums require explicit review so a new value cannot reject an otherwise valid response unnoticed.
-
Preserve existing MCP names and compatibility aliases unless a deliberate breaking change is requested and documented.
-
Run Ruff, formatting, strict mypy, the full pytest suite, package build and smoke tests, requirements export, dependency audit, and container smoke test when release readiness is in scope.
The schema workflow is documentation-only: never provide credentials, call an account endpoint, or invoke a trading mutation. Report the source URL, check date, detected drift, implementation impact, validation performed, and any remaining uncertainty.
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 · 40 lines · 50 tokens per session scan A 45fd49bddec9
trading212-api-sync is a skill published in the GitHub repository RohanAnandPandit/trading212-mcp-server (58 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 400 once invoked, about $0.0003 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-06.
Other skills, from other repositories
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
dv-connect
One-step setup for a Dataverse environment — installs tools, authenticates, registers the MCP server, and writes .env. Use when starting a new project, switching environments, fixing authentication, or troubleshooting an MCP connection that won't come up.
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…