Borrowing it
Nothing to install: this file belongs to ZhgChgLi/linkyee. 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/ZhgChgLi/linkyee/main/.claude/skills/linkyee-plugin-builder/SKILL.mdgit clone --depth 1 https://github.com/ZhgChgLi/linkyeeWrote 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/zhgchgli/linkyee/linkyee-plugin-builder)<a href="https://agentmods.dev/skills/zhgchgli/linkyee/linkyee-plugin-builder"><img src="https://agentmods.dev/badge/skills/zhgchgli/linkyee/linkyee-plugin-builder/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/zhgchgli/linkyee/linkyee-plugin-builder"><img src="https://agentmods.dev/badge/skills/zhgchgli/linkyee/linkyee-plugin-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Privilege Escalation · line 109 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00125 | $0.01891 |
| Opus 5 | $0.00063 | $0.00945 |
| Sonnet 5 | $0.00025 | $0.00378 |
| Haiku 4.5 | $0.00013 | $0.00189 |
Grade A, and why
linkyee-plugin-builder 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 10d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
linkyee Plugin Builder
You help users add build-time plugins to linkyee — a Ruby/Liquid
static-site generator. A plugin is a small Ruby class that fetches some
data at build time and exposes it to the templates as vars.<PluginName>.
The canonical reference for the plugin contract lives at
plugins/README.md. Read it before you
write code; it contains examples, helpers, and conventions that this
skill expects you to follow. Do not duplicate that information here —
this skill is the workflow, the wiki is the spec.
Mental model in one paragraph
config.yml lists enabled plugins. At build time scaffold.rb
instantiates <PluginName>.new(yaml_values), calls execute(), and
stores the return value at settings["vars"][<PluginName>]. Liquid then
renders {{ vars.<PluginName> }} (and friends) inside config.yml
strings and the theme's index.html. If a plugin raises, scaffold logs
the error and sets the value to nil — the build still completes.
Workflow
Follow these steps in order. Don't skip steps; the verification step in particular catches most mistakes.
1. Understand the request
Before writing anything, confirm:
- What data does the user want? (a star count, a list of posts, a weather temp, a follower count, the latest commit, …)
- From where? (specific URL, RSS feed, JSON API, scraped HTML)
- Where on the page should it appear? (footer, a link's text, a new
link, a new section in
index.html)
If anything is ambiguous, ask one focused question. Don't ask three clarifying questions at once.
2. Check whether a built-in plugin already covers it
Read plugins/README.md § "Built-in plugins". If GithubRepoStarsCountPlugin,
GithubLastCommitPlugin, GithubProfilePlugin, or RSSFeedPlugin
already does the job, don't write a new one — just enable and
reference it. Tell the user.
3. Read the existing config
Run Read on config.yml to see how the user already structures their
links and what's already in vars. This affects naming and where to
inject the value.
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.
- 10d ago First seen · 180 lines · 125 tokens per session scan A 10136a4334b7
linkyee-plugin-builder is a skill published in the GitHub repository ZhgChgLi/linkyee (174 stars, last pushed today), licensed MIT. It adds 125 tokens to every session and 1,891 once invoked, about $0.0006 per session on Opus 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-08-30.
Other skills, from other repositories
agent-canvas
Interactive element picker for web pages. Opens a browser with click-to-select UI overlay. Use when you need to let users visually select DOM elements, identify element selectors, or get detailed element information interactively. Triggers on "select an element", "pick element", "let me choose", "which element", or…
animated-portfolio-sites
Build a one-page animated personal or portfolio site (canvas starfield, rotating galaxies with mouse parallax, hidden accordion/card content, anchor nav) and publish it free on GitHub Pages. Covers the canvas technique and the Pages permission wall, not just one task.
just-progress-bar-skill
Design, select, generate, and audit accessible creative progress bars for React, HTML/CSS, Gallery demos, recipes, CLI workflows, and Agent/MCP integrations.
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.