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 LobsterTrap/lola --skill git-cheatsheetgit clone --depth 1 https://github.com/LobsterTrap/lolaWrote 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/lobstertrap/lola/git-cheatsheet)<a href="https://agentmods.dev/skills/lobstertrap/lola/git-cheatsheet"><img src="https://agentmods.dev/badge/skills/lobstertrap/lola/git-cheatsheet/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/lobstertrap/lola/git-cheatsheet"><img src="https://agentmods.dev/badge/skills/lobstertrap/lola/git-cheatsheet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 259 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 167 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 195 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.01396 |
| Opus 5.5 | $0.00006 | $0.00558 |
| Sonnet 5.5 | $0.00003 | $0.00279 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
git-cheatsheet 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Cheatsheet
Getting Started
Start a new repo:
git init
Clone an existing repo:
git clone <url>
Prepare to Commit
Add untracked file or unstaged changes:
git add <file>
Add all untracked files and unstaged changes:
git add .
Choose which parts of a file to stage:
git add -p
Move file:
git mv <old> <new>
Delete file:
git rm <file>
Tell Git to forget about a file without deleting it:
git rm --cached <file>
Unstage one file:
git reset <file>
Unstage everything:
git reset
Check what you added:
git status
Make Commits
Make a commit (and open text editor to write message):
git commit
Make a commit:
git commit -m 'message'
Commit all unstaged changes:
git commit -am 'message'
Move Between Branches
Switch branches:
git switch <name> OR git checkout <name>
Create a branch:
git switch -c <name> OR git checkout -b <name>
List branches:
git branch
List branches by most recently committed to:
git branch --sort=-committerdate
Delete a branch:
git branch -d <name>
Force delete a branch:
git branch -D <name>
Diff Staged/Unstaged Changes
Diff all staged and unstaged changes:
git diff HEAD
Diff just staged changes:
git diff --staged
Diff just unstaged changes:
git diff
Diff Commits
Show diff between a commit and its parent:
git show <commit>
Diff two commits:
git diff <commit> <commit>
Diff one file since a commit:
git diff <commit> <file>
Show a summary of a diff:
git diff <commit> --stat git show <commit> --stat
Ways to refer to a commit
Every time we say <commit>, you can use any of these:
a branch
main
a tag
v0.1
a commit ID
3e887ab
a remote branch
origin/main
current commit
HEAD
3 commits ago
HEAD^^^ or HEAD~3
Discard Your Changes
Delete unstaged changes to one file:
git restore <file> OR git checkout <file>
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.
- 1mo ago First seen · 325 lines · 15 tokens per session scan A d5213c7ed0a5
git-cheatsheet is a skill published in the GitHub repository LobsterTrap/lola (132 stars, last pushed 10d ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,396 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-30.
Other skills, from other repositories
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents, with ReasoningBank intelligence and multi-agent coordination. Use when designing agent memory/versioning, coordinating multiple agents over shared state, or building experience-replay and learning loops into an agentic system.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management across many GitHub repos. Use when changes span several repositories, keeping repos in sync, or planning cross-repo architecture and dependency work.
hooks-automation
Automated coordination, formatting, and learning from Claude Code operations using intelligent hooks with MCP integration. Includes pre/post task hooks, session management, Git integration, memory coordination, and neural pattern training for enhanced development workflows. Use when configuring Claude Code hooks…
verification-loop
After a feature or refactor on this Windows estate, run six checks in order and write a PASS or FAIL note before a draft pull request. Use when work is about to be committed, pushed, or handed to another harness.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…