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.
npx agentmods add agents/openclaw/acpx/grokbuildgit clone --depth 1 https://github.com/openclaw/acpxWhat 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 | $0.00000 | $0.00246 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
GrokBuild 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 2d 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 Build
- Built-in name:
grok-build - Default command:
grok agent stdio - Upstream: xAI Grok Build
acpx grok-build launches the installed grok CLI through its ACP stdio entrypoint. Install Grok Build and complete its normal authentication flow before using it through acpx.
When Grok advertises cached_token, acpx asks the Grok ACP server to authenticate with its agent-managed cached login. For non-browser and automation environments where Grok advertises xai.api_key, acpx grok-build also accepts XAI_API_KEY.
Examples:
acpx grok-build sessions new
acpx grok-build 'review this branch'
acpx grok-build exec 'summarize this repository'
If your Grok Build install exposes ACP through a different command, override the built-in in ~/.acpx/config.json:
{
"agents": {
"grok-build": {
"command": "grok agent stdio"
}
}
}
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.
- 2d ago First seen · 30 lines · 0 tokens per session scan A 355c42aebcfe
GrokBuild is an agent published in the GitHub repository openclaw/acpx (3,202 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 246 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 agents, from other repositories
code-quality-reviewer
Use this agent when you want a comprehensive review of code quality, readability, structure, and maintainability. This agent focuses on how well-written and organized code is — not on bugs, logic errors, or functional correctness. It examines file length, function complexity, naming conventions, code organization…
refactor-analyst
Use this agent when you need a thorough code quality analysis and refactoring recommendations for specific files, directories, or an entire branch. This agent reads code deeply, questions every pattern, checks for modern best practices, and produces a detailed report — without making any changes.\n\nExamples:\n\n…
typescript-type-reviewer
Use this agent when you need a thorough review of TypeScript type definitions, type usage patterns, and type architecture in recently written or modified code. This includes checking for type duplicates, unnecessary custom type copies that should be imported from libraries, improper type assertions, overly broad…
docs-researcher
Use this agent when the user needs information from project documentation files, SDK docs, protocol specs, or any @docs prefixed directories. This includes questions about API usage, SDK methods, protocol details, configuration options, type definitions, or architectural decisions documented in the codebase. The agent…
perf-deep-audit
Use this agent when you need a deep performance review of Electron, React, or Vite-related code — especially for large renders, long chat histories, streaming updates, memory leaks, IPC bottleneck analysis, or general app sluggishness investigations. This agent reviews and diagnoses only; it does not edit…
clean-code-refactor
Use this agent when you need to refactor existing code, rewrite a module for better maintainability, decompose a large file into focused sub-modules, eliminate duplication, improve type safety, optimize performance, or generally elevate code quality. This agent goes beyond the minimum ask — it proactively identifies…