Borrowing it
Nothing to install: this file belongs to inbharatai/agent-arcade-gateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/inbharatai/agent-arcade-gateway/main/CLAUDE.mdgit clone --depth 1 https://github.com/inbharatai/agent-arcade-gatewayWrote 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/instructions/inbharatai/agent-arcade-gateway/claude-md)<a href="https://agentmods.dev/instructions/inbharatai/agent-arcade-gateway/claude-md"><img src="https://agentmods.dev/badge/instructions/inbharatai/agent-arcade-gateway/claude-md/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/instructions/inbharatai/agent-arcade-gateway/claude-md"><img src="https://agentmods.dev/badge/instructions/inbharatai/agent-arcade-gateway/claude-md.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.00409 | $0.00409 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
agent-arcade-gateway CLAUDE.md 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 10d 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
Agent Arcade Gateway — Claude Code Instructions
OPENCLAW INTEGRATION TRUTH REQUIREMENT
You must audit the OpenClaw adapter against the real OpenClaw ecosystem, not against guessed interfaces. Treat the current OpenClaw integration as unverified until proven otherwise.
Rules:
- Verify the actual package and SDK surfaces used by OpenClaw.
- Do not assume any scoped package like
@openclaw/sdkexists unless it is actually resolvable and documented in the current ecosystem. - Use the real OpenClaw package (
openclaw) and real plugin SDK import surfaces (openclaw/plugin-sdk/*). - Compare the adapter's assumptions against OpenClaw's actual plugin architecture and event/runtime APIs.
- If the adapter was written against a guessed duck-typed interface rather than the real SDK, say so clearly.
- Replace incorrect package names, wrong imports, and imagined interfaces with the real ones.
- Then test against a real running OpenClaw instance if the repo/environment supports it.
- If live integration cannot be completed from the current repo/environment, do not claim success. Mark it as unverified and explain the exact blocker.
You must specifically check for:
- wrong peerDependencies
- nonexistent npm package references
- wrong import paths
- fake or assumed event names
- monkey-patching against guessed APIs instead of real plugin hooks
- adapters that are structurally plausible but never actually connected to OpenClaw
For the final report, include an explicit section:
OPENCLAW ADAPTER VERDICT
- package name currently used
- correct package name
- current import paths used
- correct import paths
- whether the adapter was connected to a real OpenClaw instance
- whether the integration is real, partial, or only conceptual
- exact fixes made
- exact validation evidence
If the adapter targets a nonexistent package or imagined SDK API, treat that as a false integration claim and fix it before any launch-readiness verdict.
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.
- 10d ago First seen · 38 lines · 409 tokens per session scan A 790c6e6bd2bc
agent-arcade-gateway CLAUDE.md is an instructions file published in the GitHub repository inbharatai/agent-arcade-gateway (5 stars, last pushed 5mo ago), licensed MIT. It adds 409 tokens to every session, about $0.0020 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.