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 luohy15/y-agent --skill devgit clone --depth 1 https://github.com/luohy15/y-agentWrote 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/luohy15/y-agent/dev)<a href="https://agentmods.dev/skills/luohy15/y-agent/dev"><img src="https://agentmods.dev/badge/skills/luohy15/y-agent/dev/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/luohy15/y-agent/dev"><img src="https://agentmods.dev/badge/skills/luohy15/y-agent/dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 136 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium Data Exfiltration · line 588 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00044 | $0.08415 |
| Opus 5.5 | $0.00018 | $0.03366 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago First seen · 617 lines · 44 tokens per session scan A 04c2852b5f5d
dev is a skill published in the GitHub repository luohy15/y-agent (220 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 8,415 once invoked, about $0.0002 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.