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 create-skillgit 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/create-skill)<a href="https://agentmods.dev/skills/codingmydna/grokers/create-skill"><img src="https://agentmods.dev/badge/skills/codingmydna/grokers/create-skill/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/create-skill"><img src="https://agentmods.dev/badge/skills/codingmydna/grokers/create-skill.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.00043 | $0.00805 |
| Opus 5.5 | $0.00017 | $0.00322 |
| Sonnet 5.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 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 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.
- 1mo 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 3mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 805 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 create-skill, 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.