Borrowing it
Nothing to install: this file belongs to djtelicloud/grok-mcp-server. 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/djtelicloud/grok-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/djtelicloud/grok-mcp-serverWrote 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/djtelicloud/grok-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/djtelicloud/grok-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/djtelicloud/grok-mcp-server/agents-md.svg" alt="Measured on agentmods" 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.00525 | $0.00525 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
grok-mcp-server 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 8d 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
Public Repository Rules
- This repository is the public, workspace-neutral UniGrok core.
- The sacred public contract is the generic experience a stranger expects after
cloning this repository and running the commands in
README.mdto use UniGrok Core on:4765. Every tracked file must support that contract or public contribution/verification of it. - Preserve one
agentharness with a zero-key local route when an operator-owned runtime is ready, optional Grok Build subscription and xAI API routes, live model discovery, explicit billing receipts, and bounded visible recovery. - Never add private intelligence, subordinate-provider orchestration, IDE state, private multi-seat topology, provider coordination, raw experiments, credentials, or user data.
- Never add symlinks, nested repositories, copied
.gitdirectories, or worktree pointers. - The repository root is the main checkout. IDE-created linked worktrees belong outside
this checkout under the parent
grok-mcp/.worktrees/directory and must not be moved manually. - New public tools require a clear public-use reason, boundary tests, and verification from a clean container.
- Preserve CLI isolation in
unigrok_public.server: disposable empty workspace, disposable configuration home, OAuth-only subprocess environment, and denied local file/shell/edit/MCP capabilities. - Generic installs use only server-owned public configuration documented in
README.mdandexample.env. Never commit a real.env. - Pass only
XAI_API_KEYinto the API process. Never pass it to the CLI child, never print it, and never place it in an IDE MCP configuration. - Do not hard-code or allowlist Grok language model ids. Discover CLI and API catalogs independently and validate explicit selections against the chosen live plane. Media model overrides remain provider-defined.
- Needle must remain visibly inactive until a real optional shadow/reflex runtime, tests, promotion boundary, and provenance receipts exist. Do not convert design or eval artifacts into a false runtime claim.
- Never commit
.env, OAuth files, tokens, logs, sessions, caches, or generated state. - Before claiming completion, run
uv run pytest -q,uv run ruff check ., the public clone-boundary checks, build the image, verify/healthz,/readyz,/runtimez, compare MCPtools/listwith self-discovery, and exercise every configured public route.
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.
- 8d ago First seen · 39 lines · 525 tokens per session scan A a72bb29566f5
grok-mcp-server AGENTS.md is an instructions file published in the GitHub repository djtelicloud/grok-mcp-server (23 stars, last pushed 18d ago), licensed MIT. It adds 525 tokens to every session, about $0.0026 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 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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.