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 rules/arcadeai/arcade-mcp/versioninggit clone --depth 1 https://github.com/ArcadeAI/arcade-mcpWhat 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.00206 | $0.00206 |
| Opus 5 | $0.00103 | $0.00103 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
versioning 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 2d 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
Versioning
This repository contains 5 libraries: arcade-core, arcade-tdk, arcade-serve, arcade-mcp-server, and arcade-mcp (CLI)
Dependency graph recap:
- arcade-core
- The base library
- arcade-tdk
- Depends on: arcade-core
- arcade-serve
- Depends on: arcade-core
- arcade-mcp-server
- Depends on: arcade-core, arcade-serve, arcade-tdk
- arcade-mcp
- Depends on: arcade-mcp-server, arcade-core
- Dev/optional deps: arcade-serve, arcade-tdk
Rules
- ALWAYS use semver (semantic versioning)
- ALWAYS increase the version of a library in pyproject.toml when a library's code is modified.
- ALWAYS increase the minimum required version of dependencies if there is a breaking change between dependencies
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.
- 2d ago First seen · 26 lines · 206 tokens per session scan A 61baed26124a
versioning is a cursor rule published in the GitHub repository ArcadeAI/arcade-mcp (1,014 stars, last pushed 2d ago), licensed MIT. It adds 206 tokens to every session, about $0.0010 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-30.
Other cursor rules, from other repositories
cursorrules
You are writing documentation for Arcade, an AI platform for developers. Follow these guidelines to maintain a consistent tone and style.
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
versioning
Semantic versioning rules for tagging releases.
versioning-and-npm-distribution
Versioning integrity and GitHub/npm distribution flow for AgentProdReady.
release-checklist
What to update with each code change or version release.
release
Cut a versioned release of harness-mini — bump VERSION, roll the CHANGELOG, tag, and publish a GitHub release. Use when shipping a new version. Wraps bin/harness.sh release; covers the human-judgment steps (semver choice, changelog curation) the script can't make.