Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/LIDR-academy/lidr-specbootnpx agentmods add skills/lidr-academy/lidr-specboot/sync-agent-symlinksWrote 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/lidr-academy/lidr-specboot/sync-agent-symlinks)<a href="https://agentmods.dev/skills/lidr-academy/lidr-specboot/sync-agent-symlinks"><img src="https://agentmods.dev/badge/skills/lidr-academy/lidr-specboot/sync-agent-symlinks/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/lidr-academy/lidr-specboot/sync-agent-symlinks"><img src="https://agentmods.dev/badge/skills/lidr-academy/lidr-specboot/sync-agent-symlinks.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.00059 | $0.00966 |
| Opus 5 | $0.00030 | $0.00483 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade B, and why
sync-agent-symlinks scanned grade B 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 12d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la .claude/skills How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync-agent-symlinks Skill
Keep agent-facing skill structures synchronized with ai-specs/skills as the canonical source.
Use this skill after any change in ai-specs/skills (new skill, removed skill, renamed skill, moved skill), especially when you need to avoid stale or broken symlinks.
Scope and Safety Rules
- Canonical source is
ai-specs/skills. - Mirror targets are:
.claude/skills.cursor/skills
- Manage only entries that are symlinks to
../../ai-specs/skills/<skill-name>. - Do not delete non-symlink directories in mirror targets unless the user explicitly asks.
- Never overwrite a real directory automatically; report it as a conflict.
Workflow
Step 1 - Build inventories
Collect three inventories:
- Canonical skills from
ai-specs/skills/*/SKILL.md - Mirror entries in
.claude/skills - Mirror entries in
.cursor/skills
From mirror entries, classify:
linked: valid symlink pointing to existing canonical skillbroken: symlink target missingorphan: symlink points to canonical namespace but skill no longer existsconflict: non-symlink entry with same name as canonical skillexternal: entry not managed by canonical symlink policy (leave unchanged)
Step 2 - Compute sync plan
For each mirror target:
to_add: canonical skills missing in mirror targetto_fix: broken canonical symlinks that should be recreatedto_remove: orphan canonical symlinks with no canonical sourceto_skip: conflicts and external entries (report only)
Step 3 - Apply sync safely
Apply changes in this order:
- Add missing symlinks:
<mirror>/<skill-name> -> ../../ai-specs/skills/<skill-name>
- Fix broken canonical symlinks:
- Remove broken link and recreate the same canonical link
- Remove orphan canonical symlinks:
- Remove symlink only if it points to canonical namespace and skill is gone
Never remove:
- non-symlink directories
- files not under canonical symlink policy
Step 4 - Verify integrity
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.
- 12d ago First seen · 136 lines · 59 tokens per session scan B aea9f4ab4db1
sync-agent-symlinks is a skill published in the GitHub repository LIDR-academy/lidr-specboot (66 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 966 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…