Borrowing it
Nothing to install: this file belongs to yyu0310/cc-to-grok-bridge. 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/yyu0310/cc-to-grok-bridge/main/AGENTS.mdgit clone --depth 1 https://github.com/yyu0310/cc-to-grok-bridgeWrote 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/yyu0310/cc-to-grok-bridge/agents-md)<a href="https://agentmods.dev/instructions/yyu0310/cc-to-grok-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/yyu0310/cc-to-grok-bridge/agents-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/yyu0310/cc-to-grok-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/yyu0310/cc-to-grok-bridge/agents-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.01736 | $0.01736 |
| Opus 5.5 | $0.00694 | $0.00694 |
| Sonnet 5.5 | $0.00347 | $0.00347 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
cc-to-grok-bridge AGENTS.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 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI assistant notes — cc-to-grok-bridge
This repo is a thin bridge: Claude Code stays the source of truth for rules, skill bodies, and hook scripts. Grok Build is a guest that reuses them.
Do
- Prefer existing scripts under
scripts/over inventing parallel tooling. - Keep defaults generic: workspace via
$CC_GROK_WORKSPACEor--workspace, never hardcode a personal machine path. - After install, remind the user to restart Grok from the workspace root.
- Never copy secrets from Claude Code config files into this repo or into git-tracked project config.
- For MCP/OAuth: you (the AI) run the install/login commands; the user only approves browser consent or provides a secret from their password manager when asked once. Do not default to “paste this long block into your terminal”.
Do not
- Modify
~/.claude/hooks/*.shbodies to “fix” Grok — use the adapter. - Write Grok-only rules into
CLAUDE.mdor CC memory sources. - Commit
.env, real MCP tokens, or personal vault paths. - Name private/personal MCP product codenames in public docs (describe traits: API-key HTTP, OAuth Google, Notion stdio, etc.).
- Push to any company GitHub org; personal public repos only when the user asks.
Compatibility (summary)
| Domain | Compatibility | Notes |
|---|---|---|
| System Prompt | High | Same workspace CLAUDE.md (compat) |
| skill | High | Same ~/.claude/commands (symlinks OK); minor frontmatter/trigger diffs |
| Memory | High | Pull + rules pointer + 3-zone layout; product search optional |
| Hooks | Medium | Adapter for payload + deny; no full CC-style ask UI |
| MCP | Medium | Manual/AI-assisted per server; claude.ai cloud connectors not portable |
| Plugins | Low | No auto-port of CC enabledPlugins; see docs/06_plugins.md |
Real-world note: bringing a CC setup into Grok Build is usually much smoother than the Antigravity/Gemini bridge path (hooks hard-block + simpler memory).
Memory (for AI)
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 · 135 lines · 1,736 tokens per session scan A 1437f620536d
cc-to-grok-bridge AGENTS.md is an instructions file published in the GitHub repository yyu0310/cc-to-grok-bridge (11 stars, last pushed 3mo ago), licensed MIT. It adds 1,736 tokens to every session, about $0.0069 per session on Opus 5.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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.