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 stranma/claude-code-python-template --skill syncgit clone --depth 1 https://github.com/stranma/claude-code-python-templateWrote 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/stranma/claude-code-python-template/sync)<a href="https://agentmods.dev/skills/stranma/claude-code-python-template/sync"><img src="https://agentmods.dev/badge/skills/stranma/claude-code-python-template/sync/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/stranma/claude-code-python-template/sync"><img src="https://agentmods.dev/badge/skills/stranma/claude-code-python-template/sync.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.00027 | $0.00491 |
| Opus 5.5 | $0.00011 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
sync 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.
What it actually says
Sync
Pre-flight workspace sync. Run this before starting any work.
Steps
-
Fetch remote refs
- Run
git fetch origin
- Run
-
Check workspace state
- Run
git statusto see dirty files, staged changes, untracked files - Run
git branch -vvto see current branch, tracking info, ahead/behind counts
- Run
-
Auto-reset to master if nothing is blocking
If ALL of the following are true, automatically run
git checkout master && git pull --rebasewithout asking:- Working tree is clean (no staged, unstaged, or untracked changes that matter)
- Current branch is NOT master (already on a feature branch that can be left)
- The feature branch has no unpushed commits (ahead 0, or branch was already merged)
If any blocker exists, do NOT auto-reset. Instead report the blocker and ask what to do:
- Dirty working tree: list the files and ask whether to stash, commit, or discard
- Unpushed commits on current branch: warn and ask whether to push first or switch anyway
- Already on master: just
git pull --rebaseto update
-
Show recent context
- Run
git log --oneline -3to show the last 3 commits (after any branch switch)
- Run
-
Output structured report
# Workspace Sync
Branch: <name> (tracking: <remote>/<branch>)
Status: <clean | N dirty files | N staged, M unstaged>
Remote: <up to date | N ahead, M behind>
## Actions Taken
- <e.g. "Switched to master and pulled 5 new commits", or "None -- already on clean master">
## Blockers (if any)
- <e.g. "Unstaged changes in .claude/settings.json -- stash, commit, or discard?">
## Recent Commits
- <hash> <message>
- <hash> <message>
- <hash> <message>
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 · 56 lines · 27 tokens per session scan A 086ad7263013
sync is a skill published in the GitHub repository stranma/claude-code-python-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 491 once invoked, about $0.0001 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
releasing-weaverse-sdks
Use when releasing @weaverse/ npm packages, bumping SDK versions, publishing to npm, or shipping the Weaverse SDKs. Triggers on "release sdk", "release weaverse", "publish packages", "release core", "release schema", "bump sdk version", "ship sdks".
docs
Documentation drift detection and sync via oma-docs. Verify mode finds broken refs in docs//.md, sync mode proposes patches for docs affected by a git diff.
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
commit
Generate Conventional Commits spec git commits (auto-separate by feature).
npm
Publish and manage packages on the npm registry (npmjs.com), publish, dist-tags, deprecate, owners, download stats, private installs. Use when the user asks to publish, release or manage an npm package, or to inspect the registry.
gitlab
Read and manage GitLab projects, issues, merge requests, and pipelines via the GitLab REST API. Use when the user asks about GitLab projects, issues, MRs, or pipelines.