Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gobing-ai/superskill/plugin install ccWrote 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/gobing-ai/superskill/grok-bot-register)<a href="https://agentmods.dev/skills/gobing-ai/superskill/grok-bot-register"><img src="https://agentmods.dev/badge/skills/gobing-ai/superskill/grok-bot-register/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/gobing-ai/superskill/grok-bot-register"><img src="https://agentmods.dev/badge/skills/gobing-ai/superskill/grok-bot-register.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.00086 | $0.04537 |
| Opus 5.5 | $0.00034 | $0.01815 |
| Sonnet 5.5 | $0.00017 | $0.00907 |
| Haiku 4.5 | $0.00009 | $0.00454 |
Grade A, and why
grok-bot-register 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 7d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grok Bot slash registration (post–superskill install)
Purpose
superskill install <plugin> --targets grok-bot writes skill files under
$SAND_DATA/workflows/ and prepares registration handoffs, but it does
not fill the chat / autocomplete by itself.
Filesystem preparation does not establish host registration. Inspect the actual
Bot's available tools, schema and ownership semantics before attempting a write.
The supplied update_state, target skill, action write contract is a hypothesis
until verified on that host. Without a supported preserving method, report pending.
This skill is the all-in-one follow-up after install/update: discover handoffs → register (or refresh) every record → report results → tell the human how to verify.
Bootstrap (critical — no / yet)
Before the first successful registration, the operator cannot rely on the
/ picker to launch this skill (/cc-grok-bot-register will not appear yet).
Valid ways to start (any one):
-
Human pastes into chat (preferred after install):
Read and follow
$SAND_DATA/workflows/cc-grok-bot-register/SKILL.md(or~/agent-data/workflows/cc-grok-bot-register/SKILL.md). Register all superskill grok-bot handoffs into the slash catalog. -
Human names it in natural language: “run cc-grok-bot-register”, “consume the superskill grok-bot handoff”, “fix empty
/after superskill install”. -
After registration and any required per-Bot enablement, verify the desktop
/entry and invoke it. Report mobile discovery and typed-id behavior only when observed on that client; neither is guaranteed here.
For a plugin-scoped install, pass --plugin <installed-plugin> when following
this file. Omit it only when the operator requests all handoffs.
Install messaging (for superskill authors): do not tell operators to
“type /cc-grok-bot-register” as the first step. Tell them to ask the Bot to
read and follow this SKILL.md (path above) or to use the NL triggers in
the description.
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.
- 7d ago Changed · +14 lines 9bfce88d2062
- 1mo ago Changed · +4 lines e19172ccc97c
- 1mo ago First seen · 366 lines · 86 tokens per session scan A 92c3475480a8
grok-bot-register is a skill published in the GitHub repository gobing-ai/superskill (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 86 tokens to every session and 4,537 once invoked, about $0.0003 per session on Opus 5.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-09-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…