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 skills add codingmydna/grokers --skill helpgit clone --depth 1 https://github.com/codingmydna/grokersWrote 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/codingmydna/grokers/help)<a href="https://agentmods.dev/skills/codingmydna/grokers/help"><img src="https://agentmods.dev/badge/skills/codingmydna/grokers/help/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/codingmydna/grokers/help"><img src="https://agentmods.dev/badge/skills/codingmydna/grokers/help.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.00053 | $0.00650 |
| Opus 5.5 | $0.00021 | $0.00260 |
| Sonnet 5.5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
help 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.
This is a copy
100% identical to help — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Grok Help
Answer the user's question about Grok setup, configuration, or features.
Steps
-
If the question is about current config (what MCP servers, models, or settings are active), read
~/.grok/config.toml. MCP servers are under[mcp_servers.*]sections. -
If the question is about how to do something (setup, adding MCP servers, creating skills, authentication, keyboard shortcuts, troubleshooting), first check the user-guide docs at
~/.grok/docs/user-guide/. The available guides are:01-getting-started.md-- Installation, first launch, basic interaction02-authentication.md-- Browser login, API keys, OIDC, external auth03-keyboard-shortcuts.md-- Complete key bindings reference04-slash-commands.md-- All / commands05-configuration.md-- config.toml, pager.toml, env vars06-theming.md-- Themes, appearance customization07-mcp-servers.md-- MCP server setup and management08-skills.md-- Creating and using skills09-plugins.md-- Plugin marketplace10-hooks.md-- Lifecycle hooks11-custom-models.md-- BYOK, Ollama, OpenAI endpoints12-project-rules.md-- AGENTS.md project rules13-memory.md-- Cross-session memory14-headless-mode.md-- CLI scripting and CI/CD15-agent-mode.md-- ACP/stdio IDE integration16-subagents.md-- Subagents and personas17-sessions.md-- Session management18-sandbox.md-- Sandbox mode19-plan-mode.md-- Plan mode20-background-tasks.md-- Background tasks and monitoring21-terminal-support.md-- tmux, SSH, truecolor, clipboard, /terminal-setup Read the relevant guide(s) for the user's question. If none match, fall back to~/.grok/README.mdfor the comprehensive reference.
-
To modify config for the user, edit
~/.grok/config.tomlwith search_replace. -
To create a skill for the user, create
~/.grok/skills/<name>/SKILL.md(read~/.grok/docs/user-guide/08-skills.mdfor the SKILL.md format).
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 · 51 lines · 53 tokens per session scan A 4595c5fc67cb
help is a skill published in the GitHub repository codingmydna/grokers (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 650 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to help, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
byok-custom-model
Register a custom LLM endpoint with your own API key for chat in Starchild. Use when adding a personal Anthropic, OpenAI, Grok, Qwen, DeepSeek, Meta (Muse Spark), NEAR AI, or Venice key as a chat model (e.g. add my Claude key, register DeepSeek, use Muse Spark 1.1).
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
byok-relay
OpenAI-compatible LLM gateway for any client-side application (browser, mobile, React Native, Flutter, VS Code extensions, browser extensions, Electron, smart TV, and more). Routes requests to OpenAI, Anthropic, Gemini, Groq, Mistral, and 200+ models, handling CORS, key encryption, and streaming without a dedicated…
pi-triage
Decide whether an upstream pi change needs porting to the Go port. Use when assessing upstream commits/PRs ("should we port X?"), or as the triage stage of /pi-sync. Outputs a WHY/WHAT/SCOPE verdict per change.
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.