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 agentmods add skills/futurejj/claude-skills/git-workflownpx skills add FutureJJ/claude-skills --skill git-workflowgit clone --depth 1 https://github.com/FutureJJ/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/skills/futurejj/claude-skills/git-workflow)<a href="https://agentmods.dev/skills/futurejj/claude-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/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 | $0.00047 | $0.00286 |
| Opus 5 | $0.00023 | $0.00143 |
| Sonnet 5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00029 |
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 3d 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.
What it actually says
Git Workflow
You are a Git expert focused on clean history and productive team workflows.
Core Principles
- Atomic commits. Each commit does one thing and the message explains why.
- Rebase for local, merge for shared. Rebase your feature branch onto main. Merge when integrating.
- Never force push shared branches. Only force push your own feature branches.
- Conventional commits.
feat:,fix:,refactor:,docs:,chore:prefixes enable automated changelogs.
Anti-Patterns
- Merge commits for every sync — use rebase to keep history linear
- Giant commits with "WIP" messages — commit small and often, squash before merge
- Committing secrets — use .gitignore and git-secrets
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Branching strategies | references/branching.md |
Trunk-based, GitFlow, workflows |
| Advanced operations | references/advanced.md |
Rebase, bisect, cherry-pick, hooks |
What ships with it
2 files 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.
- 3d ago First seen · 28 lines · 47 tokens per session scan A aca6a4af2755
git-workflow is a skill published in the GitHub repository FutureJJ/claude-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 286 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-08-31.
Other skills, from other repositories
auth-architect
Designs and implements authentication and identity systems. Covers OAuth2 and OIDC flows including authorization code, PKCE, and client credentials; JWT design including RS256 vs HS256, key rotation, token blacklisting, and refresh token strategy; RBAC and ABAC modeling; SSO with Google, GitHub, and SAML 2.0; session…
db-whisperer
Diagnoses and improves application-layer databases: Postgres, MySQL, SQLite, and MongoDB. Covers EXPLAIN ANALYZE, slow query detection, index strategy, N+1 detection, schema migrations with up/down scripts, connection pooling, replication setup, and vacuum/analyze operations. Use this skill when the user says "this…
obs-guardian
Builds observability, monitoring, alerting, and incident visibility for production systems. Covers OpenTelemetry instrumentation for traces, metrics, and logs; structured logging with JSON, correlation IDs, and sampling; Prometheus and Grafana scrape configs, dashboards, and recording rules; distributed tracing with…
api-sculptor
Designs and implements APIs: REST, GraphQL, gRPC, and WebSocket. Produces OpenAPI 3.1 specs, GraphQL SDL schemas, Protocol Buffer definitions, and working server implementations. Use this skill when the user asks about API design, endpoint structure, schema definition, versioning strategy, pagination, authentication…
pipeline-architect
Designs and implements data pipelines: ETL/ELT, streaming, batch processing, schema migrations, and data warehouse architecture. Covers Kafka, Airflow, dbt, Spark, ClickHouse, BigQuery, Snowflake, Redis Streams, and more. Use this skill when the user asks about data pipelines, ETL jobs, data transformation, streaming…
prompt-forge
Engineers and optimizes prompts for LLMs: system prompts, few-shot examples, chain-of-thought structures, agent personas, and evaluation frameworks. Use this skill when the user wants to write or improve a system prompt, design few-shot examples, create an agent persona, optimize prompt performance, set up prompt…