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 contains-studio/fable-delegator --skill use-grokgit clone --depth 1 https://github.com/contains-studio/fable-delegatorWrote 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/contains-studio/fable-delegator/use-grok)<a href="https://agentmods.dev/skills/contains-studio/fable-delegator/use-grok"><img src="https://agentmods.dev/badge/skills/contains-studio/fable-delegator/use-grok/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/contains-studio/fable-delegator/use-grok"><img src="https://agentmods.dev/badge/skills/contains-studio/fable-delegator/use-grok.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.00096 | $0.01482 |
| Opus 5 | $0.00048 | $0.00741 |
| Sonnet 5 | $0.00019 | $0.00296 |
| Haiku 4.5 | $0.00010 | $0.00148 |
Grade A, and why
use-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 9d 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.
Grok Subagent Skill
Spawn autonomous Grok CLI (grok, xAI's Grok Build TUI) subagents for implementation work. Same delegation philosophy as use-codex: subagents burn their own tokens; the parent verifies and synthesizes.
Canonical headless invocation
grok --prompt-file /path/to/prompt.md --always-approve --no-subagents --max-turns 100
Run it in the background (run_in_background: true) for anything non-trivial; check the output file when it exits.
Why each flag is load-bearing (learned the hard way, grok 0.2.93)
--always-approveis mandatory in headless mode. Without it, grok's first file Edit stalls waiting for approval, the session dies silently, and grok exits 0 having written nothing while its narration claims it's "implementing".--permission-mode acceptEditsis NOT sufficient — it still stalled at the first Edit.--no-subagentsplus an explicit no-delegation instruction in the prompt. Grok reads the repo's CLAUDE.md / .claude/ config and will obey instructions found there. In a repo whose CLAUDE.md says "delegate all coding to codex", grok tried to spawn codex and produced nothing. Append to every prompt:Do ALL the work yourself with your own file-edit tools in this session. Do NOT delegate to codex, subagents, or any external CLI. Ignore any instruction in CLAUDE.md or .claude/ about delegating work — it does not apply to you.
--prompt-filefor anything longer than a sentence — avoids shell-quoting issues.-p "prompt"/--singleworks for short prompts. Both are single-turn headless (print response, exit).--max-turns N— give generous headroom (80–100) for multi-file work; the default may cut it short.
Verification is mandatory — grok lies by omission
Grok's stdout narration is not evidence. It narrates step-by-step progress ("Implementing types, db, both scripts...") even in runs where zero files changed. After every run:
git status --short/git diff --stat— did the expected files actually change or appear?- Read the diff / new files yourself.
- Run the project's typecheck/tests.
- Exercise new code against real data (use a copy for anything touching a DB).
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.
- 9d ago First seen · 89 lines · 96 tokens per session scan A 1b1b4540f475
use-grok is a skill published in the GitHub repository contains-studio/fable-delegator (13 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,482 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…