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 compilet-dev/agent-skill-uselink --skill uselink-share-specgit clone --depth 1 https://github.com/compilet-dev/agent-skill-uselinkWrote 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/compilet-dev/agent-skill-uselink/uselink-share-spec)<a href="https://agentmods.dev/skills/compilet-dev/agent-skill-uselink/uselink-share-spec"><img src="https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-share-spec/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/compilet-dev/agent-skill-uselink/uselink-share-spec"><img src="https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-share-spec.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.00057 | $0.00742 |
| Opus 5 | $0.00028 | $0.00371 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
uselink-share-spec 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Share Spec via Uselink
Publish specs and plans from .planning/ to uselink so PMs, stakeholders, and business people can read them without cloning the repo.
When to Use
- User wants to share a spec or plan with someone outside the repo
- User says "share the versioning spec" or "publish the analytics plan"
- User wants a link to send a stakeholder for review
Prerequisites
Check CLI installed and configured before anything else:
which uselink || echo "MISSING"
test -f ~/.uselink/config.json && echo "OK" || echo "NO_CONFIG"
If uselink is missing, tell the user to install it. If config is missing, tell them to run uselink login.
Workflow
1. Find the artifact
Scan both directories:
ls .planning/specs/*.md .planning/plans/*.md 2>/dev/null
If the user gave a name (e.g. "versioning"), fuzzy-match against filenames. If multiple files match, list them and ask which one. If zero match, ask for the path.
2. Clean the title
Strip prefixes and convert to human-readable Title Case:
| Filename | Title |
|---|---|
done_04_publishing.md |
Publishing |
10_versioning.md |
Versioning |
billing-hardening.md |
Billing Hardening |
spec-11-polish-v2.md |
Polish V2 |
Rules: drop done_ prefix, drop leading number + underscore (04_), drop spec-NN- prefix, convert kebab/snake to spaces, Title Case the result.
3. Publish
uselink publish <file> --title "<clean title>"
Capture the URL from stdout.
4. Return the URL
Report the published URL to the user. If the file was a done_* spec, mention it was a completed spec.
Gotchas
done_prefix means the spec is implemented, not that it shouldn't be shared. Stakeholders often want to review completed specs for reference or onboarding. Publish it normally but mention the spec is marked as done.- The CLI config file path is
~/.uselink/config.json, not~/.config/uselink/. If the user says "I already logged in" but the config check fails, they may have installed a different version or the config landed in the wrong directory. Check both paths before giving up. - Glob for
.mdonly --.planning/also contains.htmlfiles (like the PRD). The uselink CLI handles HTML too, but the title-cleaning logic assumes markdown naming conventions. If the user asks to share an HTML file, skip the title cleaning and use the filename as-is. - Some plans have no number prefix (e.g.
public-profile.md,billing-hardening.md). The title cleaner must handle both numbered (10_versioning.md) and unnumbered (billing-hardening.md) filenames without mangling either.
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.
- 9d ago First seen · 74 lines · 57 tokens per session scan A 35a00e7380d5
uselink-share-spec is a skill published in the GitHub repository compilet-dev/agent-skill-uselink (2 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 742 once invoked, about $0.0003 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-31.
Other skills, from other repositories
social-post
A workflow for planning, writing, publishing, and evaluating social-media posts in the user's established voice. It covers Facebook, Instagram, YouTube, Threads, and X, including selected comment operations.
comfyui
Drive a local ComfyUI install for image, video, and audio generation via its HTTP API. Use WHENEVER generating, rendering, or editing images/video/audio/hero assets with ComfyUI, Z-Image, Ideogram, FLUX, LTX, Wan, or when building, parameterizing, or running ComfyUI workflows. Covers the API client, workflow JSON…
minimax-h3
Use when writing or debugging prompts for MiniMax H3 (Hailuo 3) video-with-audio generation, running the open weights locally in ComfyUI, choosing a quant or an acceleration LoRA for the VRAM you have, wiring reference-to-video with images, video or audio, or when a generated clip produces gibberish speech, drifts off…
hue
Meta-skill that generates new design language skills. Works on Claude Code and Codex. Use when the user says 'create a design skill', 'generate design language', 'new design system skill', 'design skill inspired by X', 'design skill from this screenshot', '/hue', or 'use hue'. Also triggers for 'remix my design skill'…
plan
Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.
dashmotion
Create dark-themed, animated technical diagrams as self-contained HTML+SVG files — flowcharts whose connectors visibly flow, and architecture diagrams where requests travel as light dots through the system (Diagrid/Temporal landing-page style). Use this skill whenever the user asks for a flowchart, workflow, pipeline…