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 sliamh11/Deus --skill update-skillsgit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/update-skills)<a href="https://agentmods.dev/skills/sliamh11/deus/update-skills"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/update-skills/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/sliamh11/deus/update-skills"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/update-skills.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.00016 | $0.01179 |
| Opus 5 | $0.00008 | $0.00589 |
| Sonnet 5 | $0.00003 | $0.00236 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade A, and why
update-skills 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 6d 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.
This is a copy
98% identical to update-skills — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
About
Skills are distributed as git branches (skill/*). When you install a skill, you merge its branch into your repo. This skill checks upstream for newer commits on those skill branches and helps you update.
Run /update-skills in Claude Code.
How it works
Preflight: checks for clean working tree and upstream remote.
Detection: fetches upstream, lists all upstream/skill/* branches, determines which ones you've previously merged (via merge-base), and checks if any have new commits.
Selection: presents a list of skills with available updates. You pick which to update.
Update: merges each selected skill branch, resolves conflicts if any, then validates with build + test.
Goal
Help users update their installed skill branches from upstream without losing local customizations.
Operating principles
- Never proceed with a dirty working tree.
- Only offer updates for skills the user has already merged (installed).
- Use git-native operations. Do not manually rewrite files except conflict markers.
- Keep token usage low: rely on
gitcommands, only open files with actual conflicts.
Step 0: Preflight
Run:
git status --porcelain
If output is non-empty:
- Tell the user to commit or stash first, then stop.
Check remotes:
git remote -v
If upstream is missing:
- Ask the user for the upstream repo URL.
git remote add upstream <url>
Fetch:
git fetch upstream --prune
Step 1: Detect installed skills with available updates
List all upstream skill branches:
git branch -r --list 'upstream/skill/*'
For each upstream/skill/<name>:
- Check if the user has merged this skill branch before:
git merge-base --is-ancestor upstream/skill/<name>~1 HEAD— if this succeeds (exit 0) for any ancestor commit of the skill branch, the user has merged it at some point. A simpler check:git log --oneline --merges --grep="skill/<name>" HEADto see if there's a merge commit referencing this branch.- Alternative:
MERGE_BASE=$(git merge-base HEAD upstream/skill/<name>)— if the merge base is NOT the initial commit and the merge base includes commits unique to the skill branch, it has been merged. - Simplest reliable check: compare
git merge-base HEAD upstream/skill/<name>withgit merge-base HEAD upstream/main. If the skill merge-base is strictly ahead of (or different from) the main merge-base, the user has merged this skill.
- Check if there are new commits on the skill branch not yet in HEAD:
git log --oneline HEAD..upstream/skill/<name>- If this produces output, there are updates available.
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.
- 6d ago First seen · 131 lines · 16 tokens per session scan A 9a9c2f9c8e17
update-skills is a skill published in the GitHub repository sliamh11/Deus (51 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 1,179 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to update-skills, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
github
Use gh as the primary interface for GitHub data and actions. Keep this skill focused on basic operations and command safety, not maintainer triage strategy.
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
create-pr
Create high-quality pull requests via gh pr create. Use when the user wants to create a PR, submit a PR, open a pull request, submit for review, or push changes for review. Triggers on: create a pr, create-pr, submit a pr, open a pull request, submit for review, make a pr, gh pr create.
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.