Borrowing it
Nothing to install: this file belongs to zai-one/grok-build-mcp. 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/zai-one/grok-build-mcp/main/.agents/skills/grok-mcp/SKILL.mdgit clone --depth 1 https://github.com/zai-one/grok-build-mcpWrote 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/skills/zai-one/grok-build-mcp/grok-mcp)<a href="https://agentmods.dev/skills/zai-one/grok-build-mcp/grok-mcp"><img src="https://agentmods.dev/badge/skills/zai-one/grok-build-mcp/grok-mcp/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/skills/zai-one/grok-build-mcp/grok-mcp"><img src="https://agentmods.dev/badge/skills/zai-one/grok-build-mcp/grok-mcp.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.00075 | $0.00314 |
| Opus 5 | $0.00037 | $0.00157 |
| Sonnet 5 | $0.00015 | $0.00063 |
| Haiku 4.5 | $0.00007 | $0.00031 |
Grade A, and why
grok-mcp 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
grok-mcp
Unofficial — not xAI/Grok. Auth =
grok loginonly.
Token budget protocol
grok_agent_session_beginonce (goal,host_budget=small)- Loop
grok_agent_session_next— execute only thecard(host_cmd|mcp_tool|end) - Execute cards carry a full
task; poll cards are{job_id}only - Schema / unknown-tool failure → typed consult → execute → poll → review (
references/execute.md) - When
done=true→grok_agent_session_end, then stop
Do not open references/* unless blocked. Do not re-plan. Do not pin a Grok CLI version.
Never
OAuth in config · dumps · parallel jobs · push/merge from the bridge
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/flow.md 121 B
- references/brainstorm.md 132 B
- references/execute.md 1.5 KB
- references/feedback.md 477 B
- references/hosts.md 379 B
- references/install.md 338 B
- references/operate.md 574 B
- references/security.md 155 B
- references/tools.md 507 B
- references/update.md 1.1 KB
- references/verify.md 734 B
- scripts/check_ready.sh 324 B runs code
- scripts/draft_issue.py 1.1 KB runs code
- scripts/update_mcp.sh 431 B runs code
- templates/goal-brief.md 75 B
- templates/issue.md 396 B
- templates/receipt.md 77 B
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 · 30 lines · 75 tokens per session scan A fdc8b7faa8d2
grok-mcp is a skill published in the GitHub repository zai-one/grok-build-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 314 once invoked, about $0.0004 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 skills, from other repositories
vulnerability-triage
Reference vocabulary for interpreting vulnerability findings — detector-vs-impact distinction, severity anchoring on demonstrated evidence, the eleven-item interpretation rubric, delegation transparency, primitive-extent scaling, the disqualifier taxonomy (D-0..D-4), CVSS Achievable / Environmental framing…
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
harness-design-fuzzing
Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…
memory-safety-c-cpp
Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…
gmail-query-syntax
Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose. Read this when constructing a Gmail search query string for the googleworkspace.gmailsearchmessages Code Mode call, especially when filtering by sent vs received, recency, sender, or…
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.