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 Yaomeng1749/claude-code-digital-nomad-config-pack --skill finishing-a-development-branchgit clone --depth 1 https://github.com/Yaomeng1749/claude-code-digital-nomad-config-packWrote 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/yaomeng1749/claude-code-digital-nomad-config-pack/finishing-a-development-branch)<a href="https://agentmods.dev/skills/yaomeng1749/claude-code-digital-nomad-config-pack/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/yaomeng1749/claude-code-digital-nomad-config-pack/finishing-a-development-branch/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/yaomeng1749/claude-code-digital-nomad-config-pack/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/yaomeng1749/claude-code-digital-nomad-config-pack/finishing-a-development-branch.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.00044 | $0.01084 |
| Opus 5 | $0.00022 | $0.00542 |
| Sonnet 5 | $0.00009 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
finishing-a-development-branch 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 8d 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.
- 8d ago First seen · 201 lines · 44 tokens per session scan A dd2f82c6dc85
finishing-a-development-branch is a skill published in the GitHub repository Yaomeng1749/claude-code-digital-nomad-config-pack (4 stars, last pushed 4mo ago), with no licence file. It adds 44 tokens to every session and 1,084 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
ag-rebobinar
Undo estruturado. Reverte N acoes do Claude com log detalhado do que foi desfeito. Vai alem de git checkout — rastreia mudancas por sessao, arquivo, e commit, com opcao de revert seletivo.
ag-versionar-codigo
Gerencia git - branches, commits semanticos, PRs, releases e changelog. Use ao final de cada fase ou feature para manter historico limpo.