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 pleaseai/claude-code-plugins --skill git-ai-searchgit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote 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/pleaseai/claude-code-plugins/git-ai-search)<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/git-ai-search"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/git-ai-search/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/pleaseai/claude-code-plugins/git-ai-search"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/git-ai-search.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.00013 | $0.02513 |
| Opus 5.5 | $0.00005 | $0.01005 |
| Sonnet 5.5 | $0.00003 | $0.00503 |
| Haiku 4.5 | $0.00001 | $0.00251 |
Grade A, and why
git-ai-search 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.
This is a copy
100% identical to git-ai-search — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git AI Search Skill
Search and restore AI conversation context from git history using git-ai search and git-ai continue.
Overview
Git AI tracks AI-generated code and the conversations that produced it. This skill helps you:
- Search - Find AI prompt sessions by commit, file, pattern, or author
- Continue - Restore AI session context to continue work where someone left off
- Show - View the full transcript of a specific prompt
When to Use Each Command
| You want to... | Use... |
|---|---|
| See what AI context exists for a commit | git-ai search --commit <sha> |
| See AI context for specific lines | git-ai search --file <path> --lines <range> |
| Read the full AI conversation | git-ai search --commit <sha> --verbose |
| Get machine-readable output | git-ai search --json |
| Find prompts mentioning a topic | git-ai search --pattern "keyword" |
| Continue someone's AI session | git-ai continue --commit <sha> |
| Continue working on a code region | git-ai continue --file <path> --lines <range> |
| Launch Claude with restored context | git-ai continue --commit <sha> --launch |
| View a specific prompt transcript | git-ai show-prompt <id> |
Workflow Patterns
1. Investigate a Commit
Understand what AI assistance was used in a specific commit:
# See a summary of AI sessions in the commit
git-ai search --commit abc1234
# View the full conversations
git-ai search --commit abc1234 --verbose
# Get JSON for programmatic processing
git-ai search --commit abc1234 --json | jq '.prompts | keys[]'
2. Understand a Code Region
Find what AI sessions contributed to specific lines:
# Search by file
git-ai search --file src/main.rs
# Search specific lines
git-ai search --file src/main.rs --lines 100-150
# Multiple line ranges
git-ai search --file src/main.rs --lines 50-75 --lines 200-250
3. Continue Someone's Work
Pick up where a teammate left off:
# See what they were working on
git-ai search --commit abc1234 --verbose
# Restore context and continue in your shell
git-ai continue --commit abc1234
# Or launch directly into Claude Code
git-ai continue --commit abc1234 --launch
# Or copy context to clipboard to paste elsewhere
git-ai continue --commit abc1234 --clipboard
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 · 390 lines · 13 tokens per session scan A 1838416874f4
git-ai-search is a skill published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 2,513 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-ai-search, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
change-boot
Use when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr.md, legacy .adlc/memory/chdr.md fallback) as session context; pairs…
session-wrapup
End-of-session checkpoint — append diary, update active sprint doc with interim results/retro, write tech-lead handoff, commit and push. Use before /compact or at end-of-day. Distinct from sprint-wrap-up which closes a sprint.
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.
auto-git-commiter
Use when automatically commit and push OpenClaw changes to GitHub. Enable continuous improvement with automatic versioning, changelogs, and deployment-ready commits. Use when working with auto git commiter.
handoff
Write one self-contained goal that a fresh session can continue from. Use when context is running out, before clearing a session, when usage passes 95% on a long run, or when asked for a handoff.