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/luohy15/y-agent/devnpx skills add luohy15/y-agent --skill devgit clone --depth 1 https://github.com/luohy15/y-agentWhat 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 | $0.00044 | $0.08415 |
| Opus 5 | $0.00022 | $0.04208 |
| Sonnet 5 | $0.00009 | $0.01683 |
| Haiku 4.5 | $0.00004 | $0.00842 |
Grade A, and why
dev scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
evidence, send it back. Cheap non-browser smoke (curl an API, run the test suite) stays fine. How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Skill (Coordinator)
Thin shell coordinator for development work. Manages worktree lifecycle and dispatches to the
plan / impl / review leaf skills via y chat --skill <name>. Dispatched by manager via
y chat --topic dev.
Does not read code, audit, implement, or review directly. Those are leaf-skill responsibilities. This keeps the coordinator's own context lean. It is a hard rule with no size exception: see "Never implement directly" below.
⛔ Trace isolation: never cross-trace dispatch
This is the single most important rule for the dev coordinator, and the most repeatedly violated. Read it before every dispatch.
This coordinator runs under exactly one trace: its own todo_id. That trace is a private
sub-tree.
The chat itself is bound to that trace for its whole lifetime. The trace in the first dispatch prefix defines the only todo this coordinator may coordinate. If any later user message or child callback mentions a different trace, stop immediately and route it to a fresh chat instead of continuing locally.
Hard rules:
- Every
y chat --skill plan/impl/reviewdispatch you make must carry--trace-id <your_own_todo_id>. No exceptions. - Never pass another todo's id as
--trace-id. - Never resume, reuse, or attach to a plan / impl / review session (chat id) that was created under a different trace.
- A plan note, worktree, or impl result produced under a different trace is external context only. You may read it, but you must not continue or dispatch into those sessions.
- If a task genuinely needs another todo's work, that is a separate trace with its own dev coordinator. See "New requirement inside an active coordinator chat" in Notes.
- If a callback arrives with
[trace:B]while this coordinator owns traceA, do not commit, push, update todoB, or report completion. Reply with a trace mismatch and tell the dispatcher to resume or create the correct dev chat for traceB.
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.
- yesterday First seen · 617 lines · 44 tokens per session scan A 04c2852b5f5d
dev is a skill published in the GitHub repository luohy15/y-agent (219 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 8,415 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…