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-changeloggit 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-changelog)<a href="https://agentmods.dev/skills/compilet-dev/agent-skill-uselink/uselink-changelog"><img src="https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-changelog/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-changelog"><img src="https://agentmods.dev/badge/skills/compilet-dev/agent-skill-uselink/uselink-changelog.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.00050 | $0.01320 |
| Opus 5.5 | $0.00020 | $0.00528 |
| Sonnet 5.5 | $0.00010 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
uselink-changelog 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 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.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog → Uselink
Generate formatted release notes from git history and publish as a shareable uselink page.
When to Use
- "Generate release notes for this version"
- "What shipped this week? Share it."
- "Create a changelog from v1.2 to v1.3"
- "Share what we deployed today"
Prerequisites
which uselink || echo "MISSING"
test -f ~/.uselink/config.json && echo "OK" || echo "NO_CONFIG"
Workflow
1. Determine range
Between tags:
git tag --sort=-version:refname | head -5
git log <old-tag>..<new-tag> --oneline --no-merges
Time-based (last week, last sprint):
git log --since="7 days ago" --oneline --no-merges
Since last deploy (if deploy tags exist):
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
If no range specified, default to the last 7 days.
2. Gather data
# All commits in range
git log <range> --format="%H|%an|%s|%ai" --no-merges
# PRs merged in range (if gh is available)
gh pr list --state merged --search "merged:>=<start-date>" --limit 100 \
--json number,title,author,labels,mergedAt 2>/dev/null
# Group by conventional commit type
git log <range> --oneline --no-merges | grep -c "^[a-f0-9]* feat"
git log <range> --oneline --no-merges | grep -c "^[a-f0-9]* fix"
3. Categorize changes
Group into sections by commit prefix or PR labels:
| Category | Commit prefix / label | Icon |
|---|---|---|
| New Features | feat, feature |
✨ |
| Bug Fixes | fix, bugfix |
🐛 |
| Improvements | refactor, perf, improve |
⚡ |
| Documentation | docs |
📝 |
| Infrastructure | ci, build, chore, deps |
🔧 |
| Breaking Changes | BREAKING in body, ! suffix |
⚠️ |
If commits don't follow conventional format, categorize by reading the diff.
4. Generate HTML
Write to /tmp/uselink-changelog-<version>-<timestamp>.html.
<!-- Version header -->
<div class="card">
<h3>{{VERSION_OR_TITLE}}</h3>
<p class="muted">{{DATE_RANGE}} · {{COMMIT_COUNT}} commits · {{CONTRIBUTOR_COUNT}} contributors</p>
</div>
<!-- Highlights (top 3-5 most important changes) -->
<h2>Highlights</h2>
<div class="card">
<ul>
<li><strong>{{HIGHLIGHT}}</strong> — {{ONE_SENTENCE_DESCRIPTION}}</li>
</ul>
</div>
<!-- New Features -->
<h2>✨ New Features</h2>
<div class="card">
<ul><li>{{FEATURE_DESCRIPTION}} <span class="muted">(#{{PR_NUM}})</span></li></ul>
</div>
<!-- Bug Fixes -->
<h2>🐛 Bug Fixes</h2>
<div class="card">
<ul><li>{{FIX_DESCRIPTION}} <span class="muted">(#{{PR_NUM}})</span></li></ul>
</div>
<!-- Improvements -->
<h2>⚡ Improvements</h2>
<div class="card">
<ul><li>{{IMPROVEMENT}}</li></ul>
</div>
<!-- Breaking Changes (if any) -->
<h2>⚠️ Breaking Changes</h2>
<div class="card">
<ul><li><strong>{{BREAKING}}</strong> — {{MIGRATION_NOTES}}</li></ul>
</div>
<!-- Contributors -->
<h2>Contributors</h2>
<p>{{CONTRIBUTOR_LIST}}</p>
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 · 148 lines · 50 tokens per session scan A d84004786baf
uselink-changelog is a skill published in the GitHub repository compilet-dev/agent-skill-uselink (2 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 1,320 once invoked, about $0.0002 per session on Opus 5.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
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
surface-after-care
Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf…
github-repo-care
Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files…
changelog-generator
Generate CHANGELOG.md from git history grouped by Conventional Commit types. Triggers on "generate changelog", "write changelog", "release notes".
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.