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.
git clone --depth 1 https://github.com/Global-Slice/claude-pluginWrote 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/plugins/global-slice/claude-plugin/slice-global)<a href="https://agentmods.dev/plugins/global-slice/claude-plugin/slice-global"><img src="https://agentmods.dev/badge/plugins/global-slice/claude-plugin/slice-global/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/plugins/global-slice/claude-plugin/slice-global"><img src="https://agentmods.dev/badge/plugins/global-slice/claude-plugin/slice-global.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
slice-global 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 1mo 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
{
"name": "slice-global",
"description": "Read-only access to your Slice cap table, securities, ownership, compliance, workflows, valuations, and equity plans via the Slice MCP server.",
"version": "1.0.1",
"author": {
"name": "Slice Global Equity",
"email": "[email protected]",
"url": "https://www.sliceglobal.com"
},
"homepage": "https://github.com/Global-Slice/claude-plugin",
"repository": "https://github.com/Global-Slice/claude-plugin",
"license": "MIT",
"keywords": [
"slice",
"cap-table",
"equity",
"mcp",
"finance",
"esop",
"stakeholders",
"compliance",
"workflows",
"securities",
"waterfall",
"valuations",
"board",
"presentations",
"grant-approvals"
]
}
What it installs
The manifest is a name and a version. 8 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 591 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill cap-table-analysis A 79 tokens
- Skill compliance-analysis A 98 tokens
- Skill workflows-analysis A 67 tokens
- Skill board-presentation-analysis A 61 tokens
- Skill equity-compensation-analysis A 78 tokens
- Skill funding-rounds-analysis A 80 tokens
- Skill waterfall-analysis A 58 tokens
- Skill securities-analysis B 70 tokens
- MCP server slice A not measured
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.
- 1mo ago First seen · 31 lines scan A e093004ed007
slice-global is a plugin published in the GitHub repository Global-Slice/claude-plugin (9 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
bun
Comprehensive Bun runtime toolkit covering runtime, package manager, bundler, testing, HTTP servers, WebSockets, databases, framework integrations (Hono, Next.js, Nuxt, TanStack Start, SvelteKit), deployment, and Node.js compatibility.
cloudflare-images
This skill should be used when the user asks to "upload images to Cloudflare", "implement direct creator upload", "configure image transformations", "optimize WebP/AVIF", "create image variants", "generate signed URLs", "add image watermarks", "integrate with Next.js/Remix", "configure webhooks", "debug CORS errors"…
cloudflare-queues
This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded".
cloudflare-r2
Cloudflare R2 S3-compatible object storage with SQL, Iceberg, event notifications, and automation. Use for buckets, uploads, CORS, presigned URLs, large files, S3 migration, analytics, or encountering R2ERROR, CORS failures, multipart issues.
api-gateway-configuration
Configures API gateways for routing, authentication, rate limiting, and request transformation in microservice architectures. Use when setting up Kong, Nginx, AWS API Gateway, or Traefik for centralized API management.
api-reference-documentation
Creates professional API documentation using OpenAPI specifications with endpoints, authentication, and interactive examples. Use when documenting REST APIs, creating SDK references, or building developer portals.