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.
/plugin marketplace add curiositech/some_claude_skillsnpx agentmods add plugins/curiositech/some_claude_skills/git-workflow-expertgit clone --depth 1 https://github.com/curiositech/some_claude_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/plugins/curiositech/some_claude_skills/git-workflow-expert)<a href="https://agentmods.dev/plugins/curiositech/some_claude_skills/git-workflow-expert"><img src="https://agentmods.dev/badge/plugins/curiositech/some_claude_skills/git-workflow-expert.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
git-workflow-expert 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 today.
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
{
"name": "git-workflow-expert",
"description": "Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on \"git\", \"branching strategy\", \"merge conflict\", \"rebase\", \"cherry-pick\", \"monorepo git\", \"git bisect\", \"git reflog\", \"squash commits\". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist)."
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 116 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today First seen · 5 lines scan A f92ad2780560
git-workflow-expert is a plugin published in the GitHub repository curiositech/some_claude_skills (211 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-06.
Other plugins, from other repositories
productivity
Standup reports, changelogs, and git productivity helpers.
worksync
Automatic daily work-sync log — a PostToolUse hook captures gh pr/issue create/merge/close, and a companion skill lets Claude log research/ops/checkpoint events into a dated markdown note (great for feeding standups).
simple-statusline
A simple, hackable two-line statusline for Claude Code showing model, git status, context usage, and rate limits.
squirrel
A status line for Claude Code, built for ADHD brains: context, usage limits, git state, and an alarm you cannot miss when Claude is waiting on you.
ai-workflow
AI-powered development workflow automation - Preflight code quality checks with security scanning, ship-it workflow, development principles generator, and curated CLAUDE.md behavior rules manager.
pwdev-statusline
Configure and manage Claude Code status line — installs a rich, configurable bash status bar (single-jq-pass, dynamic colors, formatted tokens, truncated paths) showing model, git branch, context usage, rate limits, and token counts.