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 FlorianBruniaux/claude-code-plugins --skill git-ai-archaeologygit clone --depth 1 https://github.com/FlorianBruniaux/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/florianbruniaux/claude-code-plugins/git-ai-archaeology)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/git-ai-archaeology"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/git-ai-archaeology/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/florianbruniaux/claude-code-plugins/git-ai-archaeology"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/git-ai-archaeology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.02641 |
| Opus 5.5 | $0.00019 | $0.01056 |
| Sonnet 5.5 | $0.00009 | $0.00528 |
| Haiku 4.5 | $0.00005 | $0.00264 |
Grade A, and why
git-ai-archaeology 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-ai-archaeology
Produces a complete analysis of AI config evolution in a git repository. Finds when each AI configuration file was created, how AI-config commit velocity evolved month by month, which PRs structured the evolution, and identifies maturity phases.
Output: a single file {output_dir}/{slug}-git-archaeology.md
Expected Input
/git-ai-archaeology repo_path=/path/to/repo [output=./talks/slug] [slug=talk-name] [since=2025-01-01]
repo_path: absolute path to the target git repo (required)output: output directory (default:./talks)slug: output filename (default: repo folder name)since: analysis start date (default: first repo commit)
Workflow
- Verify the repo: ensure the path exists and is a git repo
- Global metrics: total commits, releases, contributors, time period
- Section 1: First commits: find creation date for key AI-config paths
- Section 2: Monthly distribution: commits filtered by AI-config keywords
- Section 3: Major PRs: extract and categorize significant AI-config commits
- Section 4: CHANGELOG: if CHANGELOG.md exists, extract releases with AI mentions
- Section 5: Phases: synthesize evolution phases
- Save the output file
Step 1: Verification and Global Metrics
# Verify it's a git repo
git -C {repo_path} rev-parse --git-dir
# Global metrics
git -C {repo_path} log --oneline | wc -l # total commits
git -C {repo_path} tag --sort=version:refname | wc -l # total releases
git -C {repo_path} shortlog -sn --no-merges | wc -l # contributors
git -C {repo_path} log --pretty=format:"%ad" --date=short | tail -1 # first commit
git -C {repo_path} log --pretty=format:"%ad" --date=short | head -1 # last commit
git -C {repo_path} log --merges --oneline | wc -l # merged PRs
Step 2: Section 1: First Commits per AI-Config Path
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 · 334 lines · 47 tokens per session scan A f3f59f5522ed
git-ai-archaeology is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 2,641 once invoked, about $0.0002 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
sc-diff-report
Incremental security scan for changed files only — optimized for PR and commit-level reviews.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.
install-skill
Install a community skill pack into this fork from a GitHub repo and ship it as an auto-merged PR.
submit-hook
Submit a deployed Uniswap v4 hook to the public univ4-hooks registry - format the listing, open a PR (issue fallback) so it lists on the hook marketplace.