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/proagentstore/platform/proagentstore-mcp-operatornpx skills add ProAgentStore/platform --skill proagentstore-mcp-operatorgit clone --depth 1 https://github.com/ProAgentStore/platformWrote 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/proagentstore/platform/proagentstore-mcp-operator)<a href="https://agentmods.dev/skills/proagentstore/platform/proagentstore-mcp-operator"><img src="https://agentmods.dev/badge/skills/proagentstore/platform/proagentstore-mcp-operator.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 | $0.00046 | $0.01027 |
| Opus 5 | $0.00023 | $0.00513 |
| Sonnet 5 | $0.00009 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
proagentstore-mcp-operator 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProAgentStore MCP Operator
Use this skill when the user asks you to operate ProAgentStore through their account.
Requires an MCP client that supports OAuth or browser sign-in and access to https://mcp.proagentstore.online/mcp.
Core Rule
All live ProAgentStore account operations must go through the deployed MCP server:
https://mcp.proagentstore.online/mcp
Do not bypass MCP with direct database writes, private API calls, local secrets, or browser-only shortcuts unless the user explicitly overrides this rule.
Allowed without MCP:
- Reading and editing local repository files.
- Updating docs, tests, templates, and plugin packaging.
- Explaining how ProAgentStore MCP works.
Requires MCP:
- Creating or updating an agent in the user's ProAgentStore account.
- Subscribing to an agent.
- Running a private agent instance.
- Adding or inspecting instance knowledge.
- Reading account-specific agents, deployments, analytics, files, or messages.
Connection
Use the platform MCP endpoint:
npx mcp-remote https://mcp.proagentstore.online/mcp
If the MCP client opens a browser authorization flow, wait for the user to approve it. Do not try to extract, print, or reuse OAuth tokens manually.
Runtime Flow
Use public trial chat only for discovery:
list_agents -> chat_with_agent
Use private instance chat for the real user runtime:
list_agents -> subscribe_agent -> my_instances -> add_instance_knowledge -> chat_with_instance -> instance_messages
The private instance flow is the product path because it keeps user state, knowledge, memory, and billing credentials separate from the creator's template agent.
Use browser-capable private instances through ProAgentStore runtime tools:
subscribe_agent -> register_instance_runtime -> instance_runtime_status -> run_instance_task -> approve_instance_task -> instance_task_events
PAGS is the MCP/account control plane. The local ProAgentStore runner executes Playwright, local file uploads, screenshots, terminal actions, and approval-gated browser actions through the outbound relay opened by pags up.
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.
- 3d ago First seen · 107 lines · 46 tokens per session scan A 976333af60b0
proagentstore-mcp-operator is a skill published in the GitHub repository ProAgentStore/platform (1 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 1,027 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…