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 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/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/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="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.00070 | $0.01132 |
| Opus 5.5 | $0.00028 | $0.00453 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (163 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 1,132 once invoked, about $0.0003 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
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
finishing-a-development-branch
Use when development work is complete and you need to prepare for merge. Guides through cleanup, testing, documentation, and creating a well-structured pull request.
worktree-pr
Decide whether a task deserves its own git worktree and, if chosen, run it end to end: branch from the integration branch rather than the current tree, keep the main working copy untouched while the task runs, compare the result against the untouched baseline before declaring it done, and prepare it for a pull request…
git-workflow
Run git status / log / diff and list pull requests for the session's repo via the opendray gateway. Use whenever the user asks about "what's changed", "status", "diff", "open PRs", or wants to commit / push.
intuitive-port-worktree
Port commits or patches between worktrees when explicitly requested; preserve the target branch and unrelated edits.
intuitive-squash
Safely rewrite noisy local history into reviewable commits, with aggressive or moderate plan choices, when the user explicitly asks to squash.