Absolute Work
maddhruv/absolute
End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge.
End-to-end pipeline for adding or porting a model to MPK Runtime-V2 — from a compute-graph spec (shapes + draw.io graph + HF checkpoint + TP/EP plan) to a working multi-GPU demo.
$ npx skills add mirage-project/mirage --skill v2-model-support -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mirage-project/mirage v2-model-support --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mirage-project/mirage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/v2-model-support .claude/skills/v2-model-support && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "v2-model-support" agent skill from https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-support into .claude/skills/v2-model-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "v2-model-support", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-supportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mirage-project/mirage --skill v2-model-support -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mirage-project/mirage v2-model-support --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirage-project/mirage.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/v2-model-support .agents/skills/v2-model-support && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "v2-model-support" agent skill from https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-support into .agents/skills/v2-model-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "v2-model-support", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mirage-project/mirage --skill v2-model-support -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mirage-project/mirage v2-model-support --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirage-project/mirage.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/v2-model-support .cursor/skills/v2-model-support && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "v2-model-support" agent skill from https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-support into .cursor/skills/v2-model-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "v2-model-support", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mirage-project/mirage.git --path .claude/skills/v2-model-support--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mirage-project/mirage --skill v2-model-support -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mirage-project/mirage v2-model-support --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirage-project/mirage.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/v2-model-support .gemini/skills/v2-model-support && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "v2-model-support" agent skill from https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-support into .gemini/skills/v2-model-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "v2-model-support", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mirage-project/mirage v2-model-supportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mirage-project/mirage --skill v2-model-support -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mirage-project/mirage.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/v2-model-support .github/skills/v2-model-support && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "v2-model-support" agent skill from https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-support into .github/skills/v2-model-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "v2-model-support", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mirage-project/mirage --skill v2-model-support -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mirage-project/mirage v2-model-support --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirage-project/mirage.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/v2-model-support .opencode/skills/v2-model-support && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "v2-model-support" agent skill from https://github.com/mirage-project/mirage/tree/mpk/.claude/skills/v2-model-support into .opencode/skills/v2-model-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "v2-model-support", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
v2-model-supportEnd-to-end pipeline for adding or porting a model to MPK Runtime-V2 — from a compute-graph spec (shapes + draw.io graph + HF checkpoint + TP/EP plan) to a working multi-GPU demo.
V2 Model Support is an agent skill from mirage-project/mirage. End-to-end pipeline for adding or porting a model to MPK Runtime-V2 — from a compute-graph spec (shapes + draw.io graph + HF checkpoint + TP/EP plan) to a working multi-GPU demo. Use when bringing up a NEW model on the v2 (role-split, static-plan) runtime, when porting an existing v1 model to --use-v2, or when handed a compute-graph file and asked to make it run. Covers graph→plan, builder/demo bring-up, per-kernel authoring dispatch, the debug gate ladder, and the multi-agent/box workflow.
Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/V2_DSV3_DECODE_MASTER_PLAN.md`, `references/box-orchestration.md` and `references/debug-gates.md`).
It sits in Agent Workflows, covering End-to-end testing. It works with draw.io. The repository describes itself as: Mirage Persistent Kernel: Compiling LLMs into a MegaKernel. The licence is Apache-2.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit f9eb70c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
V2 Model Support loads about 5.3k tokens when it runs, and up to ~26k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 2,451 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mirage-project/mirage at commit f9eb70c, republished under its Apache-2.0 licence (© mirage-project). 2,451 words, ~5,309 tokens.
.claude/skills/v2-model-support/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.This is the GENERIC pipeline for putting ANY model on MPK Runtime-V2. It was distilled from
the campaign that took DeepSeek-V3 decode from a v1-only model to a full-61-layer Runtime-V2
e2e run at TP8 EP2 bs=1 (commit e31b34dd, opt-in --use-v2, default build byte-identical).
DSv3 examples below are clearly labeled worked-example material — the recipe does not depend
on them; the staged plan that drove that campaign is archived at
references/V2_DSV3_DECODE_MASTER_PLAN.md (M0→M5 ladder). A SECOND, smaller worked example
— Qwen3-8B on v2, dense, single-GPU-capable — is in §"Worked example #2" below (it is
the closest starting point for a dense-model campaign).
It is a context+phased-recipe skill: architectures vary, the PHASES and GATES do not.
Read
mpk-development-normsFIRST. This skill is the HOW (graph→plan→demo); that one is the WHERE + the PR-shape gate that decides what lands cleanly onmpkwhen the campaign is done — model code inmodels/<model>/builder.py+demo/<model>/, only GENERIC ops (never<model>_*) in sharedpersistent_kernel.py, no experiment env-vars in landed code, runtime fixes as separate PRs. During exploration keep levers env-gated default-OFF (mpk-lever-cleanup); before opening the PR, conform to the norms.
In-repo (travels with every clone): this skill's references/, the v2 runtime + kernels
(include/mirage/persistent_kernel/, tasks/blackwell_v2/), the harness
(tests/runtime_python/blackwell_v2/), both worked-example demos (demo/deepseek_v3/,
demo/qwen3/), the repo agents (.claude/agents/*.md), and the sibling skills. Machine-local
(keep working without them, as noted):
~/nebius_box.sh) and the machine inventory in references/box-orchestration.md §1-2
are SITE-SPECIFIC (placeholders in-repo; actual IPs/users/keys/paths stay in
operator-local notes — never committed); the structural rules there (§3-8: rsync/build,
session discipline, safety, testing tiers) transfer to any box. No box ⇒ single-GPU phases still run end-to-end
(Qwen3-class models need no box at TP1).~/.claude/agents/: mpk-perf-analyzer, ablation-logic-reviewer,
codex-task-dispatcher) — present only on the same user account. The repo-level roster
(.claude/agents/mpk-*, v2-*, ferret-*) travels with the clone. If
ablation-logic-reviewer is missing, run the review discipline with a general-purpose
subagent given its first-principles brief.mcp__codex__codex) — the cross-check second engine; .mcp.json is
machine-local (git-ignored). If unconfigured, reviews degrade to subagent-only — say so.~/.claude/projects/-home-muhengl-mirage/memory/) — optional context,
same-account only. The load-bearing lessons are already distilled into this suite's docs.experiment_history/ — git-ignored, so a FRESH CLONE STARTS EMPTY. That is expected:
create INDEX.md + the journal on first use (contract in Phase d); the anti-loop evidence
that must survive clones lives in v2-kernel-writing/references/m1-decode-evidence.md.references/graph-to-plan.md. If none is supplied, derive the graph from the HF
modeling_*.py and WRITE the plan doc as if you had one — the plan doc is the
contract, the drawio is just its serialization.references/box-orchestration.md). Single-GPU/local for micro-gates only.DSv3-on-v2 succeeded because it NEVER registered a live-path task without a complete v2 consumer body (a bodyless consumer silently deadlocks the whole box — see the §1.1 trap below), validated each op bit-exact in isolation BEFORE it entered the graph, and went e2e at the smallest possible slice (1 MoE layer) before scaling. Every shortcut attempted around this ladder cost days (9 debug rounds on a missing AllReduce; an iter-1 hang from re-zeroing a monotonic barrier). Do not reorder the phases.
Phase 0 GRAPH→PLAN drawio → op inventory → classify {reuse|new-kernel|fused-later}
Phase a DEMO builder-first: weights/SHARD_RULES/cache-key/lifetimes; chain of
existing v2 tasks; graph-build + test-mode gates (0-GPU first)
Phase b KERNEL per-op loop for missing/slow ops; M0→M5 staged bring-up
Phase c DEBUG the gate ladder (token-match first, TP-collective blind spot,
nondeterminism protocol, hang triage)
Phase d WORKFLOW the multi-agent perf loop + box orchestration + history contractreferences/graph-to-plan.md)name | op kind | input/output shapes AT THE CHOSEN TP/EP | dtype(s) | weight source key(s) | conversion/absorption needs | collective (none / AR / reduce-scatter / EP-dispatch) | grid intuition.M<=16 contract, embedding_v2, argmax_partial/reduce_v2,
nvshmem_tile_allreduce_v2(+residual), tensor_init_v2, mul_sum_add_v2 …).
Check runtime_header.h enums 242/243, 326-355 and tasks/blackwell_v2/..claude/skills/v2-model-support/references/ V2_<MODEL>_MASTER_PLAN.md if it should travel with the repo, scratch/ (git-ignored)
for throwaway drafts. Mirror the archived DSv3 instance
(references/V2_DSV3_DECODE_MASTER_PLAN.md). This doc is what the phase leads execute
against.references/demo-stage.md)Goal: demo/<model>/demo.py + python/mirage/mpk/models/<model>/builder.py that
BUILD the graph (no GPU needed yet) and pass test-mode with existing tasks.
FUSED_KERNEL_DEBUG_METHODOLOGY.md step 2 depends on it).MPK_CONVERT_SEMAPHORE / MPK_BUILD_CACHE_ONLY in
the reference.use_v2_runtime=args.use_v2 into
PersistentKernel(...); compile() itself runs the v2 queue plan + SMEM plan +
the §1.1 deadlock guard (persistent_kernel.py ~:5619-5640). Builder-side work is
selecting v2 task names (most *_layer wrappers self-switch on
self.use_v2_runtime) and the v2-only allocations (scratch sizing, scale packs).v2_unsafe_task_types empty (every graph-used task
type has a v2 role variant, else compile() raises instead of wedging the box);
(3) test-mode (0-GPU-graph-build + single-pass CPU-launchable subset) green.For each NEW KERNEL op, dispatch the sibling skill v2-kernel-writing
(.claude/skills/v2-kernel-writing/ — the per-kernel inner loop this pipeline plugs
into: SPEC→IMPLEMENT→WIRE→VALIDATE→PERF→REVIEW) with the op's spec row from Phase 0
(roles / SMEM regions / sync / correctness reference / validate step — the §3
template in the DSv3 master plan). For pure kernel-PERF rewrites of an op that already
passes correctness, ferret-kernel-system/kda-kernel-agent + mpk-faithful-gate
are the measurement-honest routes. Every new _v2 task touches: runtime_header.h enum +
task_register.cc register_*_v2_task (consumer body MUST begin with
emit_dep_wait_consumer_prefix) + graph.cc dispatch + runtime.cc
task_type_to_name (+ the task_offset = bid.x block for fused megas) + the
.cuh/_spec.h pair in tasks/blackwell_v2/ + the persistent_kernel.py wrapper's
"..._v2" if self.use_v2_runtime switch + the builder call site.
Stage the bring-up on the PROVEN ladder (mirror references/V2_DSV3_DECODE_MASTER_PLAN.md
— DSv3 worked example; a dense single-GPU model collapses M1 to "none" and M4/M5 shrink):
tests/runtime_python/blackwell_v2/
harness (per-op, deterministically-seeded, vs fp32 torch ref AND vs the v1 twin).__syncthreads()/256-thread bodies vs the 128-thread consumer
role → deadlock/half-compute if pasted). Validate on a TP2 micrograph (2 ranks,
known vectors, bit-exact sum on both ranks), then TP8. Do this EARLY — it de-risks
everything downstream and is the first multi-rank v2 proof.__align__(1024) extern-smem footgun is only caught in-MPK).--use-v2 --layers 3-3
TP8 EP2 bs=1, --disable-vocab-parallel-lm-head to stay on present tail tasks).
TWO hard pre-conditions: (1) reachability diff — build the sliced graph in
test-mode and diff the task list vs a full build so no head/tail seed task is
silently dropped; (2) §1.1 guard green. Correctness = the Phase-c protocol.MPK_CONVERT_SEMAPHORE=K.Per-kernel gate: test-mode numeric PASS (cos ≥ 0.999, rel_max ≤ 3e-2, no NaN, and bit-exact-vs-v1 for elementwise ops) BEFORE the task enters any e2e graph.
references/debug-gates.md BEFORE debugging anything)The distilled ladder — full checklists in the reference:
skip_after_step0 class), not a missing event.mpk-correctness-gate agent before trusting any baseline and before every
math-changing commit.The full v2-updated loop is the sibling skill v2-perf-iteration
(.claude/skills/v2-perf-iteration/) — load it to run this phase; the summary below is
orientation only.
The multi-agent loop, unchanged: profiler → (analyzer) → planner → iterator → [ablation-logic-reviewer] → implement → correctness-gate → profiler → commit-reviewer → commit → memory-keeper → decide. Standing disciplines:
ablation-logic-reviewer + a Codex MCP
cross-check before acting on it (the over-claim guard; defaults params only).--use-v2 opt-in).experiment_history/ contract: journal + INDEX row after every experiment,
ESPECIALLY NULL/REGRESS (anti-loop) — via mpk-memory-keeper.references/box-orchestration.md.A COMPLETE second instance of this pipeline's endpoint already exists for a dense model, and it is the natural starting point for any dense/single-GPU v2 campaign (e.g. Qwen3-8B throughput work):
demo/qwen3/demo.py has --use-v2 (argparse use_v2_runtime=args.use_v2 into PersistentKernel python/mirage/mpk/models/qwen3/builder.py GraphBuilder has NO v2 branches —
a wiring-style difference vs DSv3's builder-side gating). The v2 branches swap exactly the
GEMM-shaped ops to the Channel-based per-tile linear family, tiles_per_task=1:
qkv_proj + gate_up → linear_layer_v3 (linear_with_residual_layer_v3 (linear_layer_v3 (TASK_LINEAR_SM100_V3 = 244 / _WITH_RESIDUAL_ = 245). Everything else keeps its task
name and runs as the v2 role variant: rmsnorm (TASK_RMS_NORM_HOPPER_V2 326), paged
attention (TASK_ATTN_SM100_V2 329, consumer-only), silu_mul, embedding, argmax
partial/reduce. Task-plan wiring is EXPLICIT at demo level (task_graph["v2_worker_task_queues"] = build_v2_worker_task_queues(...) +
add_v2_region_smem_plan(...) before mpk.compile() — the older of the two wiring
styles (DSv3 relies on compile() doing both internally; see references/demo-stage.md §7).world_size == 1 with a local
--model-path or the HF default Qwen/Qwen3-8B; no NVSHMEM collectives exist at TP1, so
no box is needed. The tracked calibration script
tests/runtime_python/blackwell_v2/e2e_qwen3_check.sh runs v1-vs---use-v2
token+ms/tok on one local GPU (v1 reference ~4.03 ms/tok noted in its header) — NOTE it
hardcodes the original machine's PY=.../mirage/.venv/bin/python and DEMO_DIR; adjust
those two vars on a clone (it is repo code — do not expect it to self-locate).demo/qwen3/demo.py@mirage-project/runtime_refactor (head 0eadb3fd,
2026-06-11) is the same demo where the Channel-based linear was PROMOTED to be THE v2
(linear_layer_v2/linear_with_residual_layer_v2, ids 244/245; non-linear v2 ids parked
at 224-229). Read it via git show mirage-project/runtime_refactor:demo/qwen3/demo.py
(remote-add note in v2-kernel-writing/references/upstream-kernel-catalog.md, which also
catalogs every upstream v2 kernel the qwen3 path uses).v2-perf-iteration with the verdict config restated for THAT campaign
(e.g. single-GPU bs=1024 throughput instead of TP8 bs=1 tpot — restate it in every
dispatch prompt; the mpk-* defs and this suite default to the DSv3 framing).This suite runs as a nested pipeline: the TOP orchestrator (main thread or the
v2-model-support-orchestrator agent) owns phase sequencing and ALL box operations;
it dispatches ONE lead subagent per phase, and a phase lead may dispatch its own
scoped workers (per-op kernel authors, harness writers, reviewers). Hard rules:
references/box-orchestration.md.)mpk-correctness-gate, mpk-profiler,
mpk-commit-reviewer, mpk-memory-keeper, ablation-logic-reviewer,
ferret-kernel-agent/kda-kernel-agent for kernel-perf work.skip_after_step0=True is
correctness, not perf — iter-1 hang otherwise).__syncthreads() body into a 128-thread consumer role.task_offset = bid.x block in
runtime.cc (else garbage CTA index → grid-barrier deadlock).alignment=1024 in the _spec.h, and an in-MPK smoke after
every fused-mega port (the harness cannot catch misalignment of OTHER tasks).| Doc | Content |
|---|---|
references/graph-to-plan.md | drawio convention + parsing, per-rank shape derivation, DSv3 worked op table, classification decision |
references/demo-stage.md | builder anatomy, SHARD_RULES/cache-key/lifetime footguns, v2 wiring specifics |
references/debug-gates.md | the phase-c ladder as checklists, 6 gate-fidelity classes, hang triage |
references/box-orchestration.md | remote-box session playbook (setup/poll split, rsync, retries, safety) — §1-2 site-specific, §3-8 transfer |
references/V2_DSV3_DECODE_MASTER_PLAN.md | the real M0→M5 plan this skill generalizes (archived worked example) |
FUSED_KERNEL_DEBUG_METHODOLOGY.md (repo root) | the original debug order-of-operations |
../v2-perf-iteration/SKILL.md + its references/loop-agents.md | the full multi-agent loop (repo-root WORKFLOW.md is a superseded stub) |
© mirage-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (references) in .claude/skills/v2-model-support of mirage-project/mirage.
Open the folder on GitHubat commit f9eb70c
V2 Model Support next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| V2 Model Support this skillmirage-project/mirage | 2.5k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Absolute Workmaddhruv/absolute | 218 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Edt MCP New ToolDitriXNew/EDT-MCP | 295 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Sebastian ThrunK-Dense-AI/mimeo | 282 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Paceai-analyst-lab/ai-analyst | 304 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ship Featuretheexperiencecompany/gaia | 308 | — | ~2.7k | Automated safety check: Notes | Custom licence |
maddhruv/absolute
End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge.
DitriXNew/EDT-MCP
Canonical, battle-tested checklist for adding a new MCP tool to the EDT-MCP plugin the right way — the IMcpTool surface, shared resolvers, schema, registration, MANIFEST, the two MANDATORY test…
K-Dense-AI/mimeo
Applies the reasoning, principles, and mental models of Sebastian Thrun (robotics and self-driving cars pioneer, founder of Google X, Waymo, Udacity, Stanford University).
ai-analyst-lab/ai-analyst
Change how visibly Claude surfaces analytical work during L3+ analyses.
theexperiencecompany/gaia
Autonomously ship a feature end-to-end with zero human intervention: plan it, implement it, review it with a team of subagents, boot the full stack, drive it in a real browser like a user…
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
mirage-project/mirage
Runtime-V2 performance-iteration workflow. An agent skill from mirage-project/mirage.
mirage-project/mirage
Step-by-step guide for adding a new task implementation to Mirage Persistent Kernel (MPK).
mirage-project/mirage
A skill your agent uses when the user wants to design or extend a FlashAttention-style forward kernel on B200/Blackwell, involving the two MMAs QKᵀ and PV, online softmax, S/P/O in TMEM, warp roles…
mirage-project/mirage
Build or run a FAITHFUL in-MPK per-task latency gate (slowCTA at the production grid + cos) for a DeepSeek-V3 MPK decode kernel or shape.
mirage-project/mirage
A skill your agent uses when a batch of env-gated (ifdef MPKDSV3 / os.environ-controlled, default-OFF) MPK optimization levers needs to be consolidated into a single clean code path for a PR…
mirage-project/mirage
Guide for using MPK test mode to unit-test individual layers or multi-layer pipelines through the full compilation pipeline.
Works with
Categories
End-to-end pipeline for adding or porting a model to MPK Runtime-V2 — from a compute-graph spec (shapes + draw.io graph + HF checkpoint + TP/EP plan) to a working multi-GPU demo. V2 Model Support is an agent skill from mirage-project/mirage.io graph + HF checkpoint + TP/EP plan) to a working multi-GPU demo.
V2 Model Support fits situations like: bringing up a NEW model on the v2 (role-split; static-plan) runtime; porting an existing v1 model to --use-v2; handed a compute-graph file and asked to make it run.
Run `npx skills add mirage-project/mirage --skill v2-model-support -a claude-code`. Or copy the skill folder (.claude/skills/v2-model-support in mirage-project/mirage) into .claude/skills/v2-model-support in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mirage-project/mirage --skill v2-model-support -a codex`. Or copy the skill folder (.claude/skills/v2-model-support in mirage-project/mirage) into .agents/skills/v2-model-support in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mirage-project/mirage --skill v2-model-support -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/v2-model-support, .gemini/skills/v2-model-support, .github/skills/v2-model-support and .opencode/skills/v2-model-support in your project.
Going by SKILL.md and its folder, V2 Model Support needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
V2 Model Support is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 21k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with V2 Model Support: Absolute Work (maddhruv/absolute, 218 stars), Edt MCP New Tool (DitriXNew/EDT-MCP, 295 stars), Sebastian Thrun (K-Dense-AI/mimeo, 282 stars) and Pace (ai-analyst-lab/ai-analyst, 304 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mirage-project (a GitHub organization) maintains it in mirage-project/mirage, which has 2,541 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.
Source: mirage-project/mirage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.