Borrowing it
Nothing to install: this file belongs to Bottelet/DaybydayCRM. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Bottelet/DaybydayCRM/develop/.claude/skills/sync-stale-branches/SKILL.mdgit clone --depth 1 https://github.com/Bottelet/DaybydayCRMWrote 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/bottelet/daybydaycrm/sync-stale-branches)<a href="https://agentmods.dev/skills/bottelet/daybydaycrm/sync-stale-branches"><img src="https://agentmods.dev/badge/skills/bottelet/daybydaycrm/sync-stale-branches/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/bottelet/daybydaycrm/sync-stale-branches"><img src="https://agentmods.dev/badge/skills/bottelet/daybydaycrm/sync-stale-branches.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 61 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00032 | $0.00913 |
| Opus 5.5 | $0.00013 | $0.00365 |
| Sonnet 5.5 | $0.00006 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
sync-stale-branches 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 134 lines · 32 tokens per session scan A f44183f6c36b
sync-stale-branches is a skill published in the GitHub repository Bottelet/DaybydayCRM (2,329 stars, last pushed 1mo ago), with no licence file. It adds 32 tokens to every session and 913 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-30.
Other skills, from other repositories
om-auto-implement-spec
Everything tracker-facing uses the operations and guards from .ai/trackers/github.md. Resolve an automatic base branch through default-branch; never assume main or develop.
larapilot-release
Manages the versions of the product: semver releases, which story targets which version, progress and forecast per version, release notes, and Gitflow release branches. Requires releasemode=YES. Italian: release, versione, versioni, semver, note di rilascio.
git-workflow
Use when choosing a Git branching strategy or handling merge vs rebase, conflicts, stashing, undoing mistakes, and release tagging — complementing the commit/PR conventions in the git rules.
cleanup-local-branches
Use when cleaning up local Git branches after origin pruning. Deletes local branches whose upstream was deleted on origin (marked gone) and local branches with no origin counterpart that have been inactive for more than six months, while always protecting the current branch and the default branches. Previews every…
resolve-issue
Use when resolving an issue from any supported tracker (GitHub, JIRA, Bugsnag). Detects the source automatically from the provided link or ID, implements a safe fix or feature, validates with tests, and creates a pull request.
pr-staged-merge-plan
Use when a large pull request should be merged and deployed in safe parts instead of all at once. Analyzes every commit in the PR, groups them into atomic logical units that each ship independently without downtime, orders the units by dependency and rollback risk, proposes squashes for a clean human-readable history…