prompt-analysis

prompt-analysis is a skill for Claude Code from pleaseai/claude-code-plugins. It costs 10 tokens per session (4,834 once invoked), scanned B, a copy of prompt-analysis, MIT.

An analysis tool for studying AI prompts and how often AI-generated code is accepted or changed. A prompt is the instruction given to an AI system.

In plain words
What is it for?
Use it to examine prompt history, AI-versus-human code changes, acceptance rates, commits, authors, and time periods in a Git repository.
Why use it?
It helps reveal which prompting patterns lead to code developers keep, modify, or reject.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; installed under .agents/ (shared by several agents).

Part of the git-ai plugin — 3 skills shipped together

Good fit Use it to examine prompt history, AI-versus-human code changes, acceptance rates, commits, authors, and time periods in a Git repository.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pleaseai/claude-code-plugins/prompt-analysis
Install

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.

Any agent
npx skills add pleaseai/claude-code-plugins --skill prompt-analysis
Clone the repo
git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Or install git-ai, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

agentmods badge for prompt-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/prompt-analysis/github.svg)](https://agentmods.dev/skills/pleaseai/claude-code-plugins/prompt-analysis)
Your own site
<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/prompt-analysis"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/prompt-analysis/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.

agentmods 80×15 button for prompt-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/prompt-analysis"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/prompt-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,834 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.04834
Opus 5.5 $0.00004 $0.01934
Sonnet 5.5 $0.00002 $0.00967
Haiku 4.5 $0.00001 $0.00483

Measured 1mo ago against content hash 7437b81c30f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

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`
Origin

This is a copy

100% identical to prompt-analysis — 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.

plugins/git-ai/.agents/skills/prompt-analysis/SKILL.md · 588 lines

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 iteration
  • id - Unique prompt identifier
  • tool - Tool used (e.g., "claude-code", "cursor")
  • model - Model name (e.g., "claude-sonnet-4-20250514")
  • human_author - Git user who created the prompt
  • commit_sha - Associated commit (if any)
  • total_additions, total_deletions - Lines of code changed
  • accepted_lines, overridden_lines - Lines kept vs modified by human
  • accepted_rate - Ratio: accepted / (accepted + overridden)
  • messages - JSON array of the conversation
  • start_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"

Read the full file on GitHub · 588 lines

Changes

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.

  1. 1mo ago First seen · 588 lines · 10 tokens per session scan B 7437b81c30f7

Subscribe to this mod's changes

prompt-analysis is a skill published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 4,834 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 100% identical to prompt-analysis, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens