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.00113 | $0.01128 |
| Opus 5 | $0.00056 | $0.00564 |
| Sonnet 5 | $0.00023 | $0.00226 |
| Haiku 4.5 | $0.00011 | $0.00113 |
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 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.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Up To Date
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.
Proactive use
When work is about to start in a repo with a remote, invoke this without being asked: announce in one line ("Running up-to-date on ") and proceed. Proactive runs stay strictly read-only — the sync decision (step 7) still requires explicit OK.
Steps
- Confirm it's a git repo with a remote. If not, say so and stop — there's nothing to sync.
- Local state:
git status --shortandgit stash list. Note uncommitted changes, untracked files, stashes. This gates everything below. - Fetch:
git fetch --all --prune. (Fetch is safe; it changes nothing local.) - Divergence: current branch vs its upstream —
git rev-list --left-right --count @{upstream}...HEAD. Report ahead/behind. No upstream (new local branch, or detached HEAD) → that command fails; say so plainly, fall back toorigin/<default-branch>for the comparison, and note the branch is unpushed. Never report "in sync" from a failed command. - Recent activity:
git log --oneline -15on the branch, and the same for the default branch if you're not on it. Summarize what changed, not every line. - Open work (if
ghis available and the remote is GitHub):gh pr listandgh issue list. Surface anything touching the files you're about to work on. - Sync decision:
- Clean + behind only → offer
git pull --ff-only. Do it only on confirm. - Diverged (ahead and behind) → explain; recommend rebase or merge; ask.
- Dirty → do NOT pull. Report the dirty state and let the user decide.
- Clean + behind only → offer
- Library currency (only if asked or
docsarg given): for the key deps in play, use context7 (resolve-library-id → query-docs) to pull current API docs, so code targets today's API, not stale memory.
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 · 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 1mo ago), licensed MIT. It adds 113 tokens to every session and 1,128 once invoked, about $0.0006 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-30.
Other skills, from other repositories
pr-create
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
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.
watch-pr
Watch an Elixir/Phoenix PR with an Amp Orb keep-alive lease until required non-deployment CI is green and review threads are resolved. Use after opening or updating a PR.