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/EmberAGI/arbitrum-vibekitWrote 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/rules/emberagi/arbitrum-vibekit/scratchpad)<a href="https://agentmods.dev/rules/emberagi/arbitrum-vibekit/scratchpad"><img src="https://agentmods.dev/badge/rules/emberagi/arbitrum-vibekit/scratchpad/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/rules/emberagi/arbitrum-vibekit/scratchpad"><img src="https://agentmods.dev/badge/rules/emberagi/arbitrum-vibekit/scratchpad.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.00000 | $0.02109 |
| Opus 5.5 | $0.00000 | $0.00844 |
| Sonnet 5.5 | $0.00000 | $0.00422 |
| Haiku 4.5 | $0.00000 | $0.00211 |
Grade A, and why
scratchpad 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project: Refactor Agents to Use Provider Selector
Last Updated: 2025-06-20T04:45:00Z Current Role: Executor
Background and Motivation
The user wants to refactor all example and template agents to use the new provider-selector from arbitrum-vibekit-core (no scoped namespace). This change will centralize and simplify AI provider configuration, making it easier to manage API keys and switch between models. The current implementation often hardcodes provider choices (e.g., openrouter(...)), which we will replace with a unified createProviderSelector() call.
Key Challenges and Analysis
- Consistency: Ensuring all agents are updated to use the new
createProviderSelectorfunction fromarbitrum-vibekit-coreconsistently. - Configuration: The new
createProviderSelectorfunction takes an object with API keys (e.g.,openRouterApiKey,openaiApiKey,xaiApiKey,hyperbolicApiKey). While the function itself does not depend on environment variables directly, we will typically load these keys from the environment (e.g.,process.env.OPENROUTER_API_KEY) when constructing the configuration object at runtime. - Dependency Management: Each agent's
package.jsonmust depend on the latest version ofarbitrum-vibekit-coreand remove direct dependencies on provider-specific SDK packages (@openrouter/ai-sdk-provider,@ai-sdk/openai,@ai-sdk/xai,@hyperbolic/ai-sdk-provider) unless still needed elsewhere. - Scope: We need to correctly identify all agents in
typescript/examplesandtypescript/templatesthat require this refactoring.
High-level Task Breakdown
Task 1: Refactor Example Agents
- Description: Update all agents in
typescript/examples/to use thecreateProviderSelectorutility. - Success Criteria: All example agents instantiate their AI provider via
createProviderSelector()and no longer have direct dependencies on provider-specific packages like@openrouter/ai-sdk-providerfor provider instantiation. - Dependencies: None.
- Status: Not Started
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 · 164 lines · 0 tokens per session scan A 54a887af9692
scratchpad is a cursor rule published in the GitHub repository EmberAGI/arbitrum-vibekit (53 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,109 tokens. 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.