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 skills/codingmydna/grokers/create-skillnpx skills add codingmydna/grokers --skill create-skillgit clone --depth 1 https://github.com/codingmydna/grokersWhat 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.00043 | $0.00805 |
| Opus 5 | $0.00022 | $0.00402 |
| Sonnet 5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
create-skill 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.
This is a copy
100% identical to create-skill — 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill
Interactively gather requirements from the user and create a fully working Grok skill on disk.
Step 1: Gather information
Ask the user the following questions one at a time as regular conversation questions (do NOT use structured option prompts for free-text inputs):
- Skill name - ask the user to type a name. Lowercase letters (a-z), digits (0-9), and hyphens (-) only. Must start and end with a letter or digit. Must be 2-64 characters long (e.g.
deploy-k8s). Validate the name before proceeding. - Scope - present the user with two options:
- Project (Recommended):
<repo-root>/.grok/skills/<name>/SKILL.md- available only in this repo, shareable with teammates - User:
~/.grok/skills/<name>/SKILL.md- available in all projects - Default to Project if inside a git repo, otherwise User.
- Project (Recommended):
- What it should do - ask the user to describe the workflow, paste an example prompt they keep repeating, or explain the task the skill should automate.
Step 2: Draft the description
Write a description frontmatter value that includes:
- What the skill does (1-2 sentences)
- Trigger phrases and keywords so Grok knows when to auto-invoke it
- The slash command name (e.g. "Use when the user runs /deploy-k8s")
Show the drafted description to the user and let them approve or edit it.
Step 3: Create the directory
Run this bash command to create the skill directory:
mkdir -p <SKILL_DIR>
Where <SKILL_DIR> is:
- User scope:
~/.grok/skills/<name> - Project scope:
<repo-root>/.grok/skills/<name>
If the skill needs helper scripts, also create <SKILL_DIR>/scripts/.
If the skill needs reference docs, also create <SKILL_DIR>/references/.
Step 4: Write SKILL.md
Use search_replace with an empty old_string to create the file at <SKILL_DIR>/SKILL.md.
The file MUST follow this exact format:
---
name: <skill-name>
description: <the description from Step 2>
---
<markdown body with instructions, steps, code blocks>
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 · 81 lines · 43 tokens per session scan A fead9243b902
create-skill is a skill published in the GitHub repository codingmydna/grokers (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 805 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-skill, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
Best of N (parallel attempts)
Delegate N parallel subagents on the same task, then pick the best result.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.
grok-subagent
Delegate bounded coding, investigation, review, implementation, and real-time X/Reddit/web research tasks from Codex to the locally authenticated Grok Build CLI. Use when the user asks Codex to consult Grok, use Grok as a subagent, compare independent model conclusions, spend SuperGrok quota on useful project work…
grok-bridge
Delegate any substantial local task to Grok Build as one durable logical job, in a repository or a non-repository workspace, and retrieve its genuine final result across turn, token, context, and caller-session boundaries. Use when the user asks for Grok/Grok Build, an independent builder/tester/reviewer/researcher…
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).
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.