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/maxvaega/skillkit/git-helpernpx skills add maxvaega/skillkit --skill git-helpergit clone --depth 1 https://github.com/maxvaega/skillkitWhat 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.00012 | $0.00175 |
| Opus 5 | $0.00006 | $0.00088 |
| Sonnet 5 | $0.00002 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
git-helper 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 yesterday.
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 Helper Skill
You are a git workflow assistant. Help users with commit messages, branch naming, and git best practices.
Commit Message Format
Follow conventional commits specification:
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Formatting, missing semicolons, etc.
- refactor: Code restructuring without behavior change
- test: Adding or updating tests
- chore: Build process, dependencies, etc.
Format:
<type>(<scope>): <subject>
<body>
<footer>
Instructions
$ARGUMENTS
Output
Provide a well-formatted commit message or git workflow guidance.
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.
- yesterday First seen · 38 lines · 12 tokens per session scan A 3d919b4ad7aa
git-helper is a skill published in the GitHub repository maxvaega/skillkit (146 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 175 once invoked, about $0.0001 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-30.
Other skills, from other repositories
swarms
Build agents and multi-agent systems with the Swarms framework — the Agent class, tools, autonomous loops, memory, and the 15+ multi-agent architectures (SequentialWorkflow, ConcurrentWorkflow, GraphWorkflow, HierarchicalSwarm, SwarmRouter, and more). Use whenever writing, reviewing, or debugging code that imports…
code-review
Perform comprehensive code reviews focusing on best practices, security vulnerabilities, performance optimization, and maintainability.
data-visualization
Create effective data visualizations using best practices for clarity, accuracy, and visual communication of insights.
financial-analysis
Perform comprehensive financial analysis including DCF modeling, ratio analysis, and financial statement evaluation for companies and investment opportunities.
langchain
Framework for building LLM-powered applications with agents, chains, and RAG. Supports multiple providers (OpenAI, Anthropic, Google), 500+ integrations, ReAct agents, tool calling, memory management, and vector store retrieval. Use for building chatbots, question-answering systems, autonomous agents, or RAG…
analytics-instrumentation
Add product analytics (BI) events to Opik features. Use when wiring events on the frontend, the backend, or the Python SDK - all three report through Segment to PostHog.