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 hakula139/nixos-config --skill git-workflowgit clone --depth 1 https://github.com/hakula139/nixos-configWrote 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/hakula139/nixos-config/git-workflow)<a href="https://agentmods.dev/skills/hakula139/nixos-config/git-workflow"><img src="https://agentmods.dev/badge/skills/hakula139/nixos-config/git-workflow/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/hakula139/nixos-config/git-workflow"><img src="https://agentmods.dev/badge/skills/hakula139/nixos-config/git-workflow.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.00057 | $0.01240 |
| Opus 5.5 | $0.00023 | $0.00496 |
| Sonnet 5 | $0.00011 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade A, and why
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 5d 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 ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +1 lines dc8b8072abb7
- 8d ago Changed · +1 lines dbc152b5a134
- 18d ago Changed · +4 lines cab9ab18ac26
- 19d ago First seen · 48 lines · 57 tokens per session scan A dc849e377f49
git-workflow is a skill published in the GitHub repository hakula139/nixos-config (6 stars, last pushed yesterday), with no licence file. It adds 57 tokens to every session and 1,240 once invoked, about $0.0002 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-09-09.
Other skills, from other repositories
git-commit
How to write a commit message that stays meaningful after the session ends — explain WHY, follow the repository's convention, and never reference conversation-local structure like "Phase 2" or "Task 3". Load this BEFORE running git commit, whenever creating a commit, amending a commit message, or asked to "commit…
gh-cli
Standardize all GitHub work via gh CLI (repos, issues, PRs, reviews, Actions, labels, releases). Trigger on any GitHub URL (incl. deep links like /pull/123, /issues/123.
github-issue
Use when the user wants to start work on a GitHub issue, set up a worktree and development environment, plan the implementation, write tests, and create a PR. Triggers: "start issue", "work on #123", "pick up issue 123", "new issue", or /github-issue [ISSUE].
merge
Commit, rebase, and merge the current branch.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.