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 urmzd/dotfiles --skill sync-releasegit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/sync-release)<a href="https://agentmods.dev/skills/urmzd/dotfiles/sync-release"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/sync-release/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/urmzd/dotfiles/sync-release"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/sync-release.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.00136 | $0.02345 |
| Opus 5.5 | $0.00054 | $0.00938 |
| Sonnet 5.5 | $0.00027 | $0.00469 |
| Haiku 4.5 | $0.00014 | $0.00234 |
Grade A, and why
sync-release 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Universal release conventions. For language-specific build matrices, publish steps, and sr.yaml templates, see the corresponding scaffold-* skill.
Release Philosophy
- Target accessibility: build for multiple platforms (Linux, macOS, Windows)
- Users should be able to install with one command (install.sh)
- GitHub Actions where applicable (sr, fsrc, teasr expose actions)
- Every release automatically updates changelog, creates GitHub release, uploads artifacts
sr.yaml Standard Config
Canonical filename: sr.yaml (not .urmzd.sr.yml). Use sr init to generate a fully-commented config.
git:
tag_prefix: "v"
floating_tag: true
sign_tags: false
v0_protection: true
commit:
types:
minor:
- feat
patch:
- fix
- perf
- refactor
none:
- docs
- revert
- chore
- ci
- test
- build
- style
changelog:
file: CHANGELOG.md
channels:
default: stable
branch: main
content:
- name: stable
packages:
- path: .
version_files: []
stage_files: []
# publish:
# type: cargo # or npm, pypi, docker, go, custom
# workspace: true # iterate workspace members
Version Files
version_files (bumped by sr) are language-specific. See the relevant scaffold-<lang> skill for the canonical values for that ecosystem. sr auto-discovers workspace members where the ecosystem supports it (Cargo, uv, pnpm/npm).
Lock files (sr v9+)
When sr bumps a manifest, it also rewrites the matching lock file and stages it in the same chore(release) commit. The rewrite edits the lock as TOML/JSON: no cargo update, uv lock, poetry lock or npm install, and no network access.
| Lock | What sr rewrites |
|---|---|
Cargo.lock |
[[package]] entries with no source (workspace crates) |
uv.lock |
[[package]] entries whose source is editable, virtual or directory |
poetry.lock |
[[package]] entries with [package.source] type = "directory" |
package-lock.json |
root version plus packages entries for workspace members |
pnpm-lock.yaml, yarn.lock |
nothing (they store no member versions); staged unchanged |
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 Changed · +17 lines 528d62d89f41
- 1mo ago First seen · 175 lines · 136 tokens per session scan A 37fdf1a6b217
sync-release is a skill published in the GitHub repository urmzd/dotfiles (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 136 tokens to every session and 2,345 once invoked, about $0.0005 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
use-codefresh
Reference for using Codefresh via the CodeFresh CLI (run from its Docker image). Use when a Codefresh CI check is failing in a recursionpharma PR, or when working with Codefresh builds.
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.