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 thewolffish/wolffish-app --skill gitgit clone --depth 1 https://github.com/thewolffish/wolffish-appWrote 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/thewolffish/wolffish-app/git)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/git"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/git/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/thewolffish/wolffish-app/git"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/git.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.00015 | $0.01036 |
| Opus 5.5 | $0.00006 | $0.00414 |
| Sonnet 5.5 | $0.00003 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
git 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
This is a pure skill — it has no plugin of its own. It teaches the
agent how to use the shell capability's shell_exec tool to perform
Git operations the way the user prefers.
When checking repo status
- Run
git statusviashell_exec. - If something has changed, run
git diff --statfor a summary. - Run
git log --oneline -5to show recent commits. - Summarize in plain language — don't just dump the output.
When making a commit
-
Run
git statusto see what's staged vs. unstaged. -
Run
git diff --staged(orgit diffif nothing is staged yet) to see exactly what's changing. -
Generate a Conventional Commit message:
type(scope): subject. -
Show the proposed message to the user and wait for approval.
-
Only after approval, run the commit:
git commit -m "..."The commit message is the user's — don't append attribution trailers or tool credits of any kind unless they ask for one.
The safety gate may also prompt — that's expected.
-
After commit, run
git log -1 --statto confirm.
When creating a branch
- Confirm the current branch with
git branch --show-current. - Branch from
mainunless the user specifies otherwise. - Use kebab-case naming with a type prefix:
feature/<description>— new functionalityfix/<description>— bug fixchore/<description>— refactor, tooling, depsdocs/<description>— docs only
- Run
git switch -c <name>to create + switch.
When pushing
- Pushing requires explicit user approval (the safety gate enforces this).
- Never use
--forcewithout explicit instruction. Prefer--force-with-leasewhen overwriting is genuinely required. - After push, surface the GitHub/GitLab URL if the remote indicates one.
When something looks dangerous
If you're about to do something with git reset --hard, git push --force,
git clean -fd, or anything that throws away local work — stop, explain,
and ask before running.
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.
- 1mo ago Changed · -34 lines 735f802ad752
- 1mo ago Changed · +42 lines fdbe3b058c43
- 1mo ago First seen · 162 lines · 15 tokens per session scan A 07dc7c782afc
git is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed 22d ago), licensed MIT. It adds 15 tokens to every session and 1,036 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
agent-computer-use
REQUIRED for any task that involves operating a desktop application — opening apps, clicking buttons, typing into fields, pressing keys, scrolling, dragging, reading what's on screen, moving or resizing windows, or verifying state after an action. Always use the agent-cu CLI commands (open, snapshot, click, type, key…
claude-api
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks for…
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the…
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server…
figma-generate-library
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it…