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/aigorahub/elves/groknpx skills add aigorahub/elves --skill grokgit clone --depth 1 https://github.com/aigorahub/elvesWrote 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/aigorahub/elves/grok)<a href="https://agentmods.dev/skills/aigorahub/elves/grok"><img src="https://agentmods.dev/badge/skills/aigorahub/elves/grok.svg" alt="Measured on agentmods" 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.00032 | $0.00706 |
| Opus 5 | $0.00016 | $0.00353 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 today.
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.
What it actually says
Grok Build Shortcut
This is the Elves-managed Claude Code alias for /grok <instructions>.
Load the installed elves skill's Provider shortcut protocols and
references/provider-shortcuts.md. Resolve scripts/run_grok.sh from the active Elves skill root,
keep the target repository as the working directory, validate the instructions and CLI, and run
it. Preserve the runner's headless non-bypass permission posture and its high reasoning default;
do not invent a model id or turn this shortcut into an Elves main-driver route.
The runner builds argv from the flags the installed Grok Build CLI advertises: an absent safety
flag (isolated --cwd, inner --sandbox strict, headless --single, --output-format,
explicit reasoning effort) fails closed, while a quality flag the installed version dropped is
simply not passed. Auto-update is disabled through the isolated [cli] auto_update config key
rather than a removed flag. Reasoning effort defaults to high; ELVES_GROK_EFFORT selects
low, medium, high, or xhigh, and ELVES_GROK_MODEL pins a model only when the
authenticated live catalog lists it. The runner reports the CLI version, effort, model, the
authentication route the CLI itself names, and any omitted flags.
On a host that cannot nest sandboxes (macOS Seatbelt refuses a second profile inside Elves'
required outer sandbox-exec boundary), the runner fails closed with
grok_inner_sandbox_unavailable before it builds a snapshot, rather than launching with the
inner profile silently missing. Elves does not drop the inner profile to make a launch succeed,
and the outer boundary is not optional; use a Linux host with the bwrap backend or select
another review route.
The Linux
boundary omits procfs and has no /proc view; it does not receive Fugu's synthetic Codex
/proc/self/exe link.
Read-only review snapshots omit oversized binary media instead of failing the whole review. Video,
audio, presentation, archive, image, font, and 3D binaries above the per-file limit are left out and
listed in the context manifest with path, byte size, and reason; the 16 MiB per-file limit is not
raised. Source, prose instructions, executable agent configuration, and --include paths still fail
closed and ask for a derived text, image, or transcript artifact.
Grok is an optional review route, like Fugu. On any non-zero exit the runner prints one
directive line naming the reason
(quota, authentication, catalog, runner, timeout, or provider). Select another available
independent reviewer instead of stopping, record requested route, actual route, and fallback reason,
and do not claim a review ran when it did not:
python3 "$ELVES_SKILL_ROOT/scripts/cobbler_agents.py" review-route --host claude-code --requested grok --unavailable grok=<reason> --json.
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.
- today Changed · +31 lines c3d6ebb4f73b
- 6d ago First seen · 18 lines · 32 tokens per session scan A b811fc2a2672
grok is a skill published in the GitHub repository aigorahub/elves (218 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 706 once invoked, about $0.0002 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-30.
Other skills, from other repositories
speckit-workflow
Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.
delegation-principle
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
ralph-specum-start
This skill should be used only when the user explicitly asks to use $ralph-specum-start, or explicitly asks Ralph Specum in Codex to start or resume a spec.
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
ralph-specum-cancel
This skill should be used only when the user explicitly asks to use $ralph-specum-cancel, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.
ralph-specum-prototype
This skill should be used only when the user explicitly invokes $ralph-specum-prototype, or explicitly asks Ralph Specum in Codex to run, resume, quick-run, or cancel an optional prototype.