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 implgit 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/impl)<a href="https://agentmods.dev/skills/luohy15/y-agent/impl"><img src="https://agentmods.dev/badge/skills/luohy15/y-agent/impl/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/impl"><img src="https://agentmods.dev/badge/skills/luohy15/y-agent/impl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Rogue Agent · line 111 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- low Excessive Agency · line 82 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00041 | $0.01720 |
| Opus 5.5 | $0.00016 | $0.00688 |
| Sonnet 5.5 | $0.00008 | $0.00344 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
impl 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.
UI, or screenshot as routine self-verification. Cheap non-browser runtime checks (curl an How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impl Skill
Leaf skill for the implementation phase of dev work. Codes inside an existing worktree. Does
not create worktrees (the caller already created one) and does not commit or push (the
dev coordinator runs y dev commit after the impl callback).
Loaded via y chat --skill impl, usually dispatched by the dev coordinator after a plan, or
directly when the sub-tasks are already known.
Working mode
Runs inside an existing worktree; the caller passes --work-dir <worktree_path>.
Workflow
y todo get <todo_id>: read the todo desc plus the linked plan note, and locate the sub-task you are assigned.y todo activate <todo_id>: mark in progress (skip if already active).- Claim the sub-task (when parallel sub-tasks exist):
y todo update <todo_id> --progress "Claim sub-task X: brief description (chat:<to_chat> wt:<worktree_name>)". Recording the chat id and worktree lets the coordinator match commit and cleanup callbacks. - Read code, implement.
y todo update <todo_id> --progress "Finished sub-task X: brief description". What changed, what was verified, and anything the coordinator must know goes here, not in the callback.- Call back to the caller, then stop. No closing walkthrough of the change in this chat
(AGENTS.md "Callback rules"): the coordinator reads the progress note and reports to the
user.
Anything that would block the coordinator (a blocker, an unresolved choice, a follow-up it must decide on) gets one clause appended to that line; the details stay in the progress note.y chat --chat-id <from_chat> -m "impl done" \ ${Y_TOPIC:+--from-topic $Y_TOPIC} --trace-id <todo_id>
Context handoff (running low on context)
Impl is a dispatched leaf, so per AGENTS.md "Context handoff" it calls back to the
coordinator and never restarts itself. Do not spawn a successor impl
(y chat --skill impl ... --new) and do not pick up further sub-tasks. The dev coordinator
decides who continues, in which worktree, at which tier.
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 · 120 lines · 41 tokens per session scan A 4b138173af49
impl is a skill published in the GitHub repository luohy15/y-agent (220 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,720 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
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…
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…
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…