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 alonbaron/claude-skills --skill up-to-dategit clone --depth 1 https://github.com/alonbaron/claude-skillsWrote 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/alonbaron/claude-skills/up-to-date)<a href="https://agentmods.dev/skills/alonbaron/claude-skills/up-to-date"><img src="https://agentmods.dev/badge/skills/alonbaron/claude-skills/up-to-date/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/alonbaron/claude-skills/up-to-date"><img src="https://agentmods.dev/badge/skills/alonbaron/claude-skills/up-to-date.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.00083 | $0.01394 |
| Opus 5.5 | $0.00033 | $0.00558 |
| Sonnet 5.5 | $0.00017 | $0.00279 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
up-to-date 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Up To Date
!echo "--- git rev-parse --show-toplevel"; git rev-parse --show-toplevel 2>&1 || true; echo "--- git remote -v"; git remote -v 2>&1 || true; echo "--- git branch --show-current"; git branch --show-current 2>&1 || true; echo "--- git status --short"; git status --short 2>&1 || true; echo "--- git stash list"; git stash list 2>&1 || true; echo "--- git fetch --all --prune"; git fetch --all --prune 2>&1 || true; echo "--- git rev-list --left-right --count @{upstream}...HEAD"; git rev-list --left-right --count @{upstream}...HEAD 2>&1 || true; echo "--- git log --oneline -15"; git log --oneline -15 2>&1 || true; echo "--- gh pr list --limit 20"; gh pr list --limit 20 2>&1 || true; echo "--- gh issue list --limit 20"; gh issue list --limit 20 2>&1 || true
The block above is this repo's git and GitHub state, captured once before you see the rest of this skill — raw command output, not analysis.
Get current before doing work. Goal: a short situational brief so you build on the latest code with full context. Read-only by default. Never mutate a dirty tree, never force, never discard local work without explicit confirmation — that holds even when this skill fired proactively.
Reading the block
Read it; don't re-run those commands as tool calls. Only run one again if the block shows it failed for a transient reason (a network blip on fetch, say) — a missing remote, no upstream, or gh unauthenticated are expected outcomes to report, not errors to retry.
- The
rev-parseline errored → not a git repo; say so and stop, there's nothing to sync. git remote -vcame back empty → no remote; say so in one line and start the task. Skip divergence and PR/issue checks entirely.- The
@{upstream}count errored (branch never pushed, or detached HEAD) → say there is no upstream, never report that as "in sync", then rungit rev-list --left-right --count origin/HEAD...HEAD(origin/mainororigin/masteriforigin/HEADis missing) and brief against the default branch. The brief still happens before any work. - The
rev-listline failed (fresh local branch, detached HEAD) → say so plainly, note the branch is unpushed, and fall back to comparing againstorigin/<default-branch>. Never report "in sync" from a failed command. gh pr list/gh issue listerrored or came back empty (nogh, unauthenticated, non-GitHub remote) → skip that section and say so; don't guess at open work.
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 Changed · -19 lines · -30 tokens per session 80b475c6c015
- 1mo ago First seen · 95 lines · 113 tokens per session scan A 845d23700a8b
up-to-date is a skill published in the GitHub repository alonbaron/claude-skills (13 stars, last pushed 3d ago), licensed MIT. It adds 83 tokens to every session and 1,394 once invoked, about $0.0003 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-30.
Other skills, from other repositories
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
han-update-documentation
Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing…
timeline
Group the current branch's commit history into semantic phases along a timeline, and generate two review documents: architecture evolution + code review.