Borrowing it
Nothing to install: this file belongs to Dimkox/adaptive-grok-build-pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Dimkox/adaptive-grok-build-pro/main/.agents/skills/adaptive-delivery/SKILL.mdgit clone --depth 1 https://github.com/Dimkox/adaptive-grok-build-proWrote 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/dimkox/adaptive-grok-build-pro/adaptive-delivery)<a href="https://agentmods.dev/skills/dimkox/adaptive-grok-build-pro/adaptive-delivery"><img src="https://agentmods.dev/badge/skills/dimkox/adaptive-grok-build-pro/adaptive-delivery/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/dimkox/adaptive-grok-build-pro/adaptive-delivery"><img src="https://agentmods.dev/badge/skills/dimkox/adaptive-grok-build-pro/adaptive-delivery.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.00042 | $0.00851 |
| Opus 5 | $0.00021 | $0.00426 |
| Sonnet 5 | $0.00008 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
adaptive-delivery 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 12d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adaptive Delivery Controller
Inputs
Read .grok-stack/runtime/active-route.json. It contains:
- intent, domains, risk, and complexity;
- required workflow skills;
- parallel read-only analysis agents;
- exactly one write agent or no write agent;
- independent review agents;
- quality profiles, human gates, and evidence kinds.
Do not substitute your own generic workflow when a route exists.
1. Establish the run
- Run
python scripts/grok_status.py. - Load every skill named in
workflow_skills. - For
standardandhigh-riskwork, create a durable change package:
python scripts/grok_change.py start
- Use the change package for scope, requirements, architecture, tests, decisions, release, rollback, and human approval evidence.
Micro changes may stay in chat if they are genuinely bounded, but still require verification and selected reviews.
2. Parallel analysis
Dispatch all analysis_agents whose work is independent. Give each agent:
- route ID and task;
- exact repository root;
- active change path when available;
- one narrow question;
- a report destination under
<change>/evidence/analysis-<agent>.md.
Wait for all reports. Synthesize facts, conflicts, and unresolved decisions. Do not ask the user for facts recoverable from the repository.
Dispatch every analysis_agents entry in one wave. The route already caps that list (default 10); do not spawn extra names to fill the cap. Keep exactly one write owner.
3. Scope and design gate
Write or update the change brief, acceptance criteria, architecture, risk, and test plan.
When human_gates contains scope_and_design_approval, present the decision and stop before implementation. For ordinary low/medium-risk tasks without a named gate, proceed after recording a bounded design.
Transition durable changes:
python scripts/grok_change.py transition <change-id> scoped --reason "scope and acceptance criteria written"
python scripts/grok_change.py transition <change-id> approved --reason "approved or no named human gate"
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.
- 12d ago First seen · 104 lines · 42 tokens per session scan A 2feb27acc95a
adaptive-delivery is a skill published in the GitHub repository Dimkox/adaptive-grok-build-pro (2 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 851 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-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…
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…