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/codealive-ai/ai-driven-development/repo-activity-summarynpx skills add CodeAlive-AI/ai-driven-development --skill repo-activity-summarygit clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-developmentWrote 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/codealive-ai/ai-driven-development/repo-activity-summary)<a href="https://agentmods.dev/skills/codealive-ai/ai-driven-development/repo-activity-summary"><img src="https://agentmods.dev/badge/skills/codealive-ai/ai-driven-development/repo-activity-summary.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.00070 | $0.01132 |
| Opus 5 | $0.00035 | $0.00566 |
| Sonnet 5 | $0.00014 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
repo-activity-summary 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Activity Summary
Answer "what's been happening in this repo" from local git history — no network, no tokens, no setup.
Trigger conditions
Use this skill when the user asks:
- "What has this repo been working on recently?"
- "What technologies does this project use?"
- "Where are the high-churn files / hotspots?"
- "Who's contributing and what are they working on?"
- "Is this project actively maintained?"
- Before onboarding onto an unfamiliar codebase.
Do not use this skill for file-level blame or provenance — use investigating-repository-history for that.
Quick start
python3 scripts/activity_summary.py --repo-dir . --days 90
| Flag | Default | Description |
|---|---|---|
--repo-dir |
. |
Path to the git repository |
--days |
90 |
Days of history to analyze |
--author |
(all) | Filter to one author |
--format |
markdown |
markdown, json, or text |
--max-commits |
500 |
Cap for very active repos |
--branch |
(current) | Branch / revision to analyze (must not start with -) |
--output / -o |
(stdout) | Write the report to a file (UTF-8) |
--classify-threshold |
0.25 |
If the share of unclassified commits exceeds this fraction, mark work-type classification unreliable and emit subject samples |
--max-unclassified-samples |
40 |
Cap on unclassified commit subjects included in the report |
--raw-subjects |
off | Emit every filtered commit subject with sha and date for agent-side classification |
--version |
— | Print version (1.1.0) and exit |
What it produces
A structured report with:
- Overview — commit count, date range, contributors, lines added/deleted
- Technologies — languages and frameworks inferred from file paths (heuristic)
- Work type breakdown — feature / bugfix / refactor / docs / infra / release / … (keyword heuristic)
- Unclassified subjects — when keyword classification is unreliable, the raw subjects so the agent can classify them
- Churn hotspots — most frequently modified files and directories (lockfiles/generated paths excluded)
- Contributor patterns — per-author commits, lines, and primary focus
- Velocity — commits/week, active days, average commit size (same noise filter as churn)
- Project health — test modules (by basename/path convention), CI, docs, recency
What ships with it
3 files 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.
- 5d ago First seen · 85 lines · 70 tokens per session scan A 2b4290960ecb
repo-activity-summary is a skill published in the GitHub repository CodeAlive-AI/ai-driven-development (132 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,132 once invoked, about $0.0003 per session on Opus 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
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-task
Execute a single subtask from an existing MAP plan via Actor and Monitor. Use when map-plan has decomposed work and you want fine-grained control over one subtask. Do NOT use without an existing plan; run map-plan first.
map-wayfind
Decision-frontier wayfinding: build and work a durable map of open design decisions BEFORE planning, for large or foggy efforts where /map-plan would force premature decomposition. Use when a task is too big or too vague to decompose — many unknowns, tangled decisions, or "I'm not even sure what to build yet" — and…
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
axum-idioms
Axum HTTP framework patterns — routing, extractors, middleware, state management. For Rust see rust-idioms.
nextjs-idioms
Next.js App Router, RSC, Server Actions, ISR. For React see react-idioms. For TypeScript see typescript-idioms.