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 ChloeVPin/open-agent-skills --skill safe-git-workflowgit clone --depth 1 https://github.com/ChloeVPin/open-agent-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/chloevpin/open-agent-skills/safe-git-workflow)<a href="https://agentmods.dev/skills/chloevpin/open-agent-skills/safe-git-workflow"><img src="https://agentmods.dev/badge/skills/chloevpin/open-agent-skills/safe-git-workflow.svg" alt="Measured on agentmods" 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.00056 | $0.01064 |
| Opus 5 | $0.00028 | $0.00532 |
| Sonnet 5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
safe-git-workflow 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.
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.
- 6d ago First seen · 69 lines · 56 tokens per session scan A 7576a43c3eaf
safe-git-workflow is a skill published in the GitHub repository ChloeVPin/open-agent-skills (2 stars, last pushed 7d ago), with no licence file. It adds 56 tokens to every session and 1,064 once invoked, about $0.0003 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-31.
Other skills, from other repositories
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
code-quality-review
Checklist and method for reviewing code quality — readability, maintainability, SOLID, DRY, performance, and backward compatibility. Use when asked to review code, a diff, a branch, or a merge request for quality, or before finalizing significant changes. For GitHub PR review use the built-in /review; for…
lunar-attribution
Add Lunar attribution when creating a pull request or issue. Use whenever the user asks to open or create a PR or issue.
dirty-worktree-discipline
Keeps agent work safe in messy repositories. Use when git status is dirty, unrelated files exist, generated artefacts are present, multiple agents share a repo, or you must commit only the intended slice without damaging someone else's work.
gjalla-prepare-and-commit
Make sure your code is ready to commit, then stage changes into clean, atomic commit. Use before committing.
github
Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.