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 makigjuro/cloudstack-ai-plugins --skill mcp-toolsgit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWrote 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/makigjuro/cloudstack-ai-plugins/mcp-tools)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/mcp-tools"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/mcp-tools/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/makigjuro/cloudstack-ai-plugins/mcp-tools"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/mcp-tools.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01155 |
| Opus 5.5 | $0.00024 | $0.00462 |
| Sonnet 5.5 | $0.00012 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
mcp-tools 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tool Usage
When the context7, Playwright, or Mermaid Chart MCP tools are available, prefer them over CLI equivalents: they return structured data and handle authentication.
Note: Servers bundled by a plugin are exposed as
mcp__plugin_<plugin>_<server>__<tool>— context7 ships with dev-workflow, dotnet-architect, and react-developer; Playwright ships with react-developer. Servers the user configured themselves use the shortmcp__<server>__<tool>form (e.g.mcp__playwright__browser_navigate), so use whichever variant is present. Mermaid Chart and github-mcp-server are user-configured and optional. If a referenced MCP tool is not available, fall back to the CLI equivalent.
context7 — Library Documentation
Before scaffolding code that uses a library, look up the current API to avoid outdated patterns.
When to use:
- Scaffolding code that uses frameworks or libraries (EF Core, Express, Django, Spring Boot, etc.)
- Debugging library-specific errors
- Checking if a library has a built-in feature before writing custom code
- Researching library capabilities during feature planning
How to use:
- Resolve the library ID:
mcp__plugin_dev-workflow_context7__resolve-library-idwith the library name - Query docs:
mcp__plugin_dev-workflow_context7__query-docswith the library ID and your question
Don't look up docs for every trivial operation — use it when the pattern is non-obvious, when hitting an error, or when a library feature might already exist for what you're building.
playwright — Browser Automation
Use for frontend verification, smoke testing, interactive CRUD verification, and visual confirmation.
When to use:
- After
/run-local— navigate to the app and verify it loaded - After
/add-feature— screenshot the new page with/screenshotor/verify-feature - During
/smoke-test— verify routes render, auth works, and CRUD flows succeed - During
/verify-feature— auto-detect changed routes, screenshot, check console/network - During
/complete-task— browser verification when frontend files changed - Debugging frontend issues — take screenshots, check console errors, inspect network
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 · 105 lines · 61 tokens per session scan A a2e074529fdb
mcp-tools is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,155 once invoked, about $0.0002 per session on Opus 5.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-10-21.
Other skills, from other repositories
wiki-serve
Start the wiki web server — browsable Wikipedia-style UI with live research, split-pane editor, AI assist, and themes. Manual trigger only: /wiki-serve, 'start wiki server', 'browse the wiki'.
demo-video
Orchestrates building a narrated demo video of a project — reads the codebase, writes a storyboard, prepares deterministic app state, drives the UI with Playwright to record clips (web and Electron, recorded by Playwright or by OBS), generates ElevenLabs voiceover, reconciles measured durations into a timeline, and…
demo-capture
Records demo video clips by driving a running app — one clip per storyboard section, with human-feeling pointer motion, dwell timing, and per-character typing. Covers who drives the app (the Playwright MCP for web, a launched Electron app, or an already-running app attached over CDP) and what records it (Playwright…
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
kubescape
Check Kubernetes manifests, Helm charts, Kustomize overlays and live clusters against NSA-CISA, MITRE ATT&CK, CIS (EKS, AKS, GKE, vanilla) and SOC2 with the Kubescape CLI. Covers framework choice, score and severity gates, PR gates that fail only on new findings (--baseline), exceptions that actually suppress…