grok

A conversation tool for capturing knowledge from the current chat as a lesson, recurring pattern, or decision.

In plain words
What is it for?
Use it to save things you learned, patterns you noticed, or decisions made during a project.
Why use it?
It helps turn useful discussion into a recorded takeaway instead of leaving it buried in the conversation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/vladolaru/claude-code-plugins/grok
Any agent
npx skills add vladolaru/claude-code-plugins --skill grok
Clone the repo
git clone --depth 1 https://github.com/vladolaru/claude-code-plugins

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.01464
Opus 5 $0.00010 $0.00732
Sonnet 5 $0.00004 $0.00293
Haiku 4.5 $0.00002 $0.00146

Measured 3d ago against content hash 51abac7a5073, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

grok 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 3d 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.

plugins/dex/codex-skills/grok/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Codex Host Adapter

This skill is generated from the canonical Claude Code command named above. To execute it in Codex:

  1. Treat the text supplied after the skill mention as the invocation arguments. Substitute that exact text for ${CODEX_SKILL_ARGUMENTS} before executing shell commands.
  2. Resolve CODEX_PLUGIN_ROOT to the absolute plugin root. The loaded skill directory is <plugin-root>/codex-skills/<skill-name>, so the plugin root is two directories above the directory containing this SKILL.md.
  3. Assign both variables explicitly in any shell call that uses them. Codex does not export these instruction variables automatically.
  4. Use Codex's available user-input and subagent tools when the workflow requests them.
  5. Follow the canonical workflow below without skipping its gates or artifact checks.

Canonical Workflow

$dex:grok

Deeply understand the current conversation, classify the knowledge, and delegate to the right capture flow. This command asks one question, then hands off - keep it fast.

digraph grok_routing {
    "Start" [shape=doublecircle];
    "Agent behavior topic?" [shape=diamond];
    "Delegate to $dex:sharpen" [shape=doublecircle];
    "Knowledge signals found?" [shape=diamond];
    "Nothing to capture" [shape=doublecircle];
    "Classify type" [shape=box];
    "Confirm with user" [shape=box];
    "User selected?" [shape=diamond];
    "Reusability signals?" [shape=diamond];
    "Upgrade to pattern?" [shape=diamond];
    "Execute $dex:learn" [shape=doublecircle];
    "Execute $dex:pattern" [shape=doublecircle];
    "Execute $dex:research" [shape=doublecircle];
    "Execute decision flow" [shape=doublecircle];

    "Start" -> "Agent behavior topic?";
    "Agent behavior topic?" -> "Delegate to $dex:sharpen" [label="yes"];
    "Agent behavior topic?" -> "Knowledge signals found?" [label="no"];
    "Knowledge signals found?" -> "Nothing to capture" [label="none"];
    "Knowledge signals found?" -> "Classify type" [label="found"];
    "Classify type" -> "Confirm with user";
    "Confirm with user" -> "User selected?";
    "User selected?" -> "Reusability signals?" [label="Learning"];
    "User selected?" -> "Execute $dex:pattern" [label="Pattern"];
    "User selected?" -> "Execute decision flow" [label="Decision"];
    "User selected?" -> "Execute $dex:research" [label="Research"];
    "Reusability signals?" -> "Upgrade to pattern?" [label="yes"];
    "Reusability signals?" -> "Execute $dex:learn" [label="no"];
    "Upgrade to pattern?" -> "Execute $dex:pattern" [label="yes"];
    "Upgrade to pattern?" -> "Execute $dex:learn" [label="no (default)"];
}

Read the full file on GitHub · 127 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 3d ago First seen · 127 lines · 20 tokens per session scan A 51abac7a5073

Subscribe to this mod's changes

grok is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,464 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens