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/scalixworld/scalix-cloud-mcpWrote 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/commands/scalixworld/scalix-cloud-mcp/setup)<a href="https://agentmods.dev/commands/scalixworld/scalix-cloud-mcp/setup"><img src="https://agentmods.dev/badge/commands/scalixworld/scalix-cloud-mcp/setup/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/commands/scalixworld/scalix-cloud-mcp/setup"><img src="https://agentmods.dev/badge/commands/scalixworld/scalix-cloud-mcp/setup.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.00023 | $0.00416 |
| Opus 5.5 | $0.00009 | $0.00166 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade B, and why
setup scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
2. **Verify the endpoint.** Call the open MCP discovery (no auth needed): `curl -s -X POST https://api.scalix.world/v1/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'` and conf Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Verify the endpoint.** Call the open MCP discovery (no auth needed): `curl -s -X POST https://api.scalix.world/v1/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'` and conf What it actually says
Walk the user through connecting to Scalix Cloud. Follow these steps in order and report each result plainly:
- Check for a key. Look for
SCALIX_API_KEYin the environment. If absent, tell the user to create one at https://console.scalix.world/org/keys and export it asSCALIX_API_KEY. Never echo the key's value back. - Verify the endpoint. Call the open MCP discovery (no auth needed):
curl -s -X POST https://api.scalix.world/v1/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'and confirm a non-empty tool catalog comes back. Report the count you actually get rather than checking it against a number — the catalog grows. This proves connectivity independent of the key. (The plain-HTTPGET /api/v1/mcplisting requires auth — don't use it for this step.) - Verify the key. Make one authenticated call (for example
POST https://api.scalix.world/api/v1/sqlwith{"query": "SELECT 1"}). A401means a bad or missing key — say so and stop; anything else confirms the connection. - MCP tools. Remind the user this plugin already ships the MCP server config; after setting the env var they may need to restart Claude Code for the
scalixserver to connect. - CLI (optional). If the user wants the terminal workflow:
npm install -g scalix-cloud, thenscalix-cloud loginandscalix-cloud whoami.
If every step passes, summarise what is now available: the platform MCP tools (however many step 2 returned), the REST API, and the CLI if installed.
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 Changed ad5735e86add
- 1mo ago First seen · 14 lines · 23 tokens per session scan B 2871e17616bd
setup is a command published in the GitHub repository scalixworld/scalix-cloud-mcp (2 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 416 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
api-aqa-flow-project-config-loading
Phase 0 Project Config Loading of api-aqa-flow (USER INTERACTION CONDITIONALLY REQUIRED).
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
api-aqa-flow-data-collection
Phase 1 Data Collection of api-aqa-flow.
api-aqa-flow-api-spec-analysis
Phase 2 API Spec Analysis of api-aqa-flow.
api-aqa-flow-gap-and-requirements-clarification
Phase 3 Gap & Requirements Clarification of api-aqa-flow (USER INTERACTION REQUIRED).
api-aqa-flow-test-case-specification
Phase 4 Test Case Specification of api-aqa-flow (HITL APPROVAL GATE).