Borrowing it
Nothing to install: this file belongs to akaghef/M3E. 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/akaghef/M3E/main/.claude/skills/sort-task/SKILL.mdgit clone --depth 1 https://github.com/akaghef/M3EWrote 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/akaghef/m3e/sort-task)<a href="https://agentmods.dev/skills/akaghef/m3e/sort-task"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/sort-task/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/akaghef/m3e/sort-task"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/sort-task.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.00224 | $0.02305 |
| Opus 5.5 | $0.00090 | $0.00922 |
| Sonnet 5.5 | $0.00045 | $0.00461 |
| Haiku 4.5 | $0.00022 | $0.00231 |
Grade A, and why
sort-task 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 5d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sort-task — タスク依存の整理と出力
相互依存のあるタスク群を DAG として projects/deps.json に書き出し、
その DAG を 3 つの形式(md / chat / map)で出力する。
構成
.claude/skills/sort-task/
├── SKILL.md ← この文書
├── deps.py ← CLI(DAG 操作・クエリ)
└── render_map.mjs ← M3E マップへの書き出し
データ: projects/deps.json(single source of truth)
依存: Python 3.10+ / networkx / Node.js
入力
- 直接列挙: 「タスク A, B, C, D の依存を整理」
- ファイル参照: 「
backlog/pj-vision-100.mdの 1–10 を DAG 化」 - 差分追加: 「PJ-09 を追加、PJ-01 の後・PJ-02 の前」
- 既存更新: 「PJ-04 state を active に」「PJ-06→PJ-07 のエッジ削除」
動作手順
- 入力特定 — ソースとタスク ID 規則を確認(既定:
PJ-NN) - タスク列挙 — 各タスクに
id/title/state(省略時draft) /priority - 依存推論 — 明示指示 > 推論。確信がない依存は review pool へ
- deps.json 更新 —
deps.py add/dep/rm-dep/state/rmで最小差分 - 検証 —
deps.py check(cycle / unknown state / 参照切れ) - 出力 — 下記 3 モードから要求されたものを生成
出力モード
| モード | 宛先 | 用途 |
|---|---|---|
| chat | 会話応答 | 対話中の確認・要約 |
| md | projects/sort-task.md 等 |
永続ドキュメント化・レビュー用 |
| map | M3E SortedTaskView |
視覚的確認・探索 |
指定がない場合は chat を既定。md や map は明示指示されたら実行。
chat
deps.py の非 JSON 出力をそのまま要約:
追加: 3 node / 5 edge
critical path: PJ-01 → PJ-04 → PJ-07
layers:
L0: PJ-01 PJ-06 PJ-08 PJ-04
L1: PJ-03 PJ-02 PJ-07
ready: PJ-01 PJ-06 PJ-08 PJ-04
review pool(自信のない依存候補):
[ ] PJ-05 → PJ-03 ? (ObserveSelf の出力を DogfoodDeep が使う可能性)
md
# DAG: {title} から始まる以下のフォーマット:
# DAG: projects/deps.json
最終更新: 2026-04-17
## critical path
PJ-01 → PJ-03
## layers
- L0 (parallel): PJ-01, PJ-04, PJ-06, PJ-08, PJ-00, PJ-05
- L1 (parallel): PJ-02, PJ-03, PJ-07
## ready
PJ-01, PJ-04, PJ-06, PJ-08, PJ-00, PJ-05
## nodes
| id | title | state | layer | prereqs |
|----|-------|-------|-------|---------|
| PJ-01 | TrustEng | draft | L0 | — |
| PJ-03 | DogfoodDeep | draft | L1 | PJ-01 |
...
書き出し先はユーザ指定(例: backlog/sort-task-2026-04-17.md)。指定が無ければ聞く。
map
node .claude/skills/sort-task/render_map.mjs を実行。
What ships with it
2 files 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.
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.
- 5d ago First seen · 190 lines · 224 tokens per session scan A 5576e10c81d0
sort-task is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 224 tokens to every session and 2,305 once invoked, about $0.0009 per session on Opus 5.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-10-02.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…