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/git-ai-project/git-ai/prompt-analysisnpx skills add git-ai-project/git-ai --skill prompt-analysisgit clone --depth 1 https://github.com/git-ai-project/git-aiWrote 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/git-ai-project/git-ai/prompt-analysis)<a href="https://agentmods.dev/skills/git-ai-project/git-ai/prompt-analysis"><img src="https://agentmods.dev/badge/skills/git-ai-project/git-ai/prompt-analysis.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.00010 | $0.04834 |
| Opus 5 | $0.00005 | $0.02417 |
| Sonnet 5 | $0.00002 | $0.00967 |
| Haiku 4.5 | $0.00001 | $0.00483 |
Grade B, and why
prompt-analysis scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**User:** `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Analysis Skill
Analyze AI prompting patterns using the local prompts.db SQLite database.
What is Git AI?
Git AI is a tool that tracks AI-generated code and prompts in git. It stores:
- Every AI conversation (prompts and responses)
- Which lines of code came from AI vs human edits
- Acceptance rates (how much AI code was kept vs modified)
- Associated commits and authors
This skill queries that data to help users understand their AI coding patterns.
Initialization
First, determine scope from the user's question:
| User mentions | Flags to use |
|---|---|
| "my prompts" or nothing specified | (default - current user, current repo) |
| "team", "everyone", "all authors" | --all-authors |
| specific person's name | --author "<name>" |
| specific time range | --since <days> (default: 30) |
Discovery is notes-only — git-ai prompts always operates on the current repository (the working directory must be inside a git repo). To analyze multiple repos, run the command separately in each.
Run initialization:
git-ai prompts [flags]
This creates/updates prompts.db in the current directory.
Schema Reference
The prompts table contains:
seq_id- Auto-increment ID for iterationid- Unique prompt identifiertool- Tool used (e.g., "claude-code", "cursor")model- Model name (e.g., "claude-sonnet-4-20250514")human_author- Git user who created the promptcommit_sha- Associated commit (if any)total_additions,total_deletions- Lines of code changedaccepted_lines,overridden_lines- Lines kept vs modified by humanaccepted_rate- Ratio: accepted / (accepted + overridden)messages- JSON array of the conversationstart_time,last_time- Unix timestamps
Analysis Approaches
For aggregate questions (metrics, comparisons)
Use direct SQL queries:
git-ai prompts exec "SELECT model, AVG(accepted_rate), COUNT(*) FROM prompts GROUP BY model"
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 · 588 lines · 10 tokens per session scan B 7437b81c30f7
prompt-analysis is a skill published in the GitHub repository git-ai-project/git-ai (2,525 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 4,834 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentproto-llm-endpoint
Use the local LLM endpoint proxy (localhost:18090) — or your own gated public deployment — to route Claude Code / Claude SDK through custom providers (OpenRouter, Moonshot, Groq, ZAI) via an Anthropic-compatible gateway. Covers adapter-specific behaviors, auth patterns, proxy codenames, and common failure modes.
orcho-prompt-engine
Use for Orcho prompt authoring/rendering internals: orcho-core/pipeline/prompts/, orcho-core/core/prompts/, prompt templates/contracts, cache-aware rendering, session/delta prompt metadata, prompt snapshots, and prompt boundary tests. Pair with evidence/observability only when rendered prompt data is stored as…
prompt-engineering
Expert prompt engineering guidance with proven techniques and anti-patterns. Invoke this skill whenever writing, editing, reviewing, or refining any prompt that will be interpreted by an AI model — system prompts, agent instructions, tool-use prompts, command templates, multi-step task prompts, or agentic workflows.…
content-image
Image prompt engineering for AI image generation models. Use when user wants to generate images, create image prompts, or optimize prompts for DALL-E, Midjourney, Stable Diffusion, or other image generation tools.
cache-identical-fork-prefix-construction
Build forked conversation prefixes that stay identical across turns so prompt caching keeps working.
deepstream-sop
Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…