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 zachdunn/grok-plugin-claude-code --skill grok-promptinggit clone --depth 1 https://github.com/zachdunn/grok-plugin-claude-codeWrote 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/zachdunn/grok-plugin-claude-code/grok-prompting)<a href="https://agentmods.dev/skills/zachdunn/grok-plugin-claude-code/grok-prompting"><img src="https://agentmods.dev/badge/skills/zachdunn/grok-plugin-claude-code/grok-prompting/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/zachdunn/grok-plugin-claude-code/grok-prompting"><img src="https://agentmods.dev/badge/skills/zachdunn/grok-plugin-claude-code/grok-prompting.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.00073 | $0.00534 |
| Opus 5 | $0.00036 | $0.00267 |
| Sonnet 5 | $0.00015 | $0.00107 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
grok-prompting 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 9d 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 prompting
Grok runs the delegated task in a single headless pass — there is no back-and-forth to clarify. The prompt has to carry everything Grok needs. Shape the user's request into a crisp task before forwarding it; do not do the task yourself.
What a good Grok task prompt contains
- The goal, in one sentence. What should be true when Grok is done.
- Where to work. Name the directory, package, or files when known. Grok
starts from the run's
cwdand reads from there. - Constraints. What it may and may not touch; conventions to follow; anything to leave alone.
- Acceptance criteria. How Grok (and the user) will know it worked — "tests pass", "tsc clean", "the endpoint returns 200", a specific behavior.
- Done-ness. For a write task, ask for the edits plus a short summary of what changed. For a read task, ask for the specific answer/finding format.
Keep it tight
- Prefer concrete nouns (file paths, function names, error text) over vague description. Paste the actual error, not a paraphrase.
- State the outcome, not a step-by-step procedure — let Grok plan the steps.
- One task per run. Bundle only tightly-related changes.
- Pick the mode deliberately: write-capable (default) to make changes,
--readfor review/diagnosis/research with no edits. - Reach for
--effort highon genuinely hard problems; leave it default otherwise. Use--checkwhen correctness matters more than latency.
Anti-patterns
- Don't forward a one-word ask ("fix it") — add the goal and acceptance check.
- Don't include routing flags (
--read,--effort, …) inside the task text; they are controls, not instructions for Grok. - Don't ask Grok to do exploratory work the main thread should just do itself — delegate substantial, bounded tasks, not trivial lookups.
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.
- 9d ago First seen · 43 lines · 73 tokens per session scan A e3c6f4a0fc53
grok-prompting is a skill published in the GitHub repository zachdunn/grok-plugin-claude-code (30 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 534 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-30.
Other skills, from other repositories
grok-prompting
Internal guidance for composing clear Grok task prompts from Codex rescue handoffs.
grok-prompting
Internal guidance for composing Grok Build prompts for coding, review, diagnosis, and research tasks inside the Grok Claude Code plugin.
grok-prompting
Internal guidance for composing sharp Grok prompts for consultation and review inside the Grok plugin.
gpt-5-4-prompting
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Grok Codex plugin.
forge
Reference-grounded prompt-artifact formation. Reads a target reference doc, surfaces the under-determined contract coordinates, and projects a ready-to-use prompt or standing skill recipe.
zero-shot
Use when the user asks to "check zero-shot", "audit few-shot anchoring", "find example anchoring", or invokes /zero-shot. Read-only audit of LLM-facing prose: principle over anchoring examples.