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 cobusgreyling/grok-build-showcase --skill skill-craftergit clone --depth 1 https://github.com/cobusgreyling/grok-build-showcaseWrote 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/cobusgreyling/grok-build-showcase/skill-crafter)<a href="https://agentmods.dev/skills/cobusgreyling/grok-build-showcase/skill-crafter"><img src="https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/skill-crafter/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/cobusgreyling/grok-build-showcase/skill-crafter"><img src="https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/skill-crafter.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.00092 | $0.00801 |
| Opus 5 | $0.00046 | $0.00400 |
| Sonnet 5 | $0.00018 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
skill-crafter 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Crafter
You produce skills that are immediately useful, auto-discoverable, and follow the exact conventions from the official Grok Build skills guide.
Required Output Format
Every skill you create must contain:
---
name: kebab-case-name
description: >
One or two sentence description that is specific enough for automatic
invocation. Include example trigger phrases the user might say.
when-to-use: Optional but recommended — explicit trigger phrases.
argument-hint: "<example usage>"
metadata:
short-description: "Very short label (optional)"
---
# Human Friendly Title
Intro paragraph.
## Steps (or Usage / Workflow)
1. Numbered, concrete actions.
2. Each step should mention tools by name when relevant
(`read_file`, `grep`, `spawn_subagent`, `run_terminal_command`, `write`, etc.).
3. Include success criteria or "what good looks like".
## Principles / Important Notes (recommended)
- Anti-hallucination, safety, or verification rules.
- References to other skills or AGENTS.md sections when useful.
Creation Process
-
Clarify the workflow the skill should capture.
- Ask for (or infer) the exact trigger phrases users will say.
- Identify the primary tools the skill will use.
-
Write excellent
descriptiontext.- It must be specific. Bad: "Helps with commits". Good: "Create well-formatted git commits following conventional commit standards. Use when the user wants to commit changes or asks for /commit."
-
Structure the body:
- Start with a short purpose.
- Use numbered steps (the agent loves ordered procedures).
- Include verbatim prompts, command examples, or output formats where the skill needs precision.
- Add "Important Principles" or "Verification" sections for non-trivial skills.
-
Make it self-contained but reference official docs or other skills when relevant (e.g. "follow the todo discipline in AGENTS.md").
-
After writing the file, suggest how the user can test it:
/skills <new-name>- Run a small task that should trigger it automatically.
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.
- 11d ago First seen · 89 lines · 92 tokens per session scan A 72f51e45fba1
skill-crafter is a skill published in the GitHub repository cobusgreyling/grok-build-showcase (2 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 801 once invoked, about $0.0005 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-31.
Other skills, from other repositories
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
coordinate
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…