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 laurigates/dotfiles --skill repo-activitygit clone --depth 1 https://github.com/laurigates/dotfilesWrote 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/laurigates/dotfiles/repo-activity)<a href="https://agentmods.dev/skills/laurigates/dotfiles/repo-activity"><img src="https://agentmods.dev/badge/skills/laurigates/dotfiles/repo-activity.svg" alt="Measured on agentmods" 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.00065 | $0.00780 |
| Opus 5 | $0.00032 | $0.00390 |
| Sonnet 5 | $0.00013 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
repo-activity 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 7d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Activity Overview
Scan all repositories in ~/repos/ and report recent activity.
Workflow
1. Find All Git Repositories
fd -t d -H -I '^\.git$' ~/repos --max-depth 4 -x dirname {} | sort -u
Both flags are load-bearing, and omitting either fails silently — you get a short repo list that reads as a quiet portfolio rather than a broken scan:
-I(--no-ignore):~/reposis itself a git repo whose.gitignoreis default-deny (/*, allowlisting only the portfolio config). Without-I,fdhonors it and finds 1 repo instead of 124.--max-depth 4: nested packs live one level deeper than theowner/repolayout —laurigates/comfyui-nodes/comfyui-touch-resize,ForumViriumHelsinki/simpl-open/user-manual. Depth 3 finds 98, depth 4 finds 124.
Sanity-check the count before reporting: fewer than ~50 repos means the scan is broken, not that the portfolio is small.
2. Get Activity for Each Repo
For each repository, gather:
# Last commit date and message
git -C {repo} log -1 --format='%ar|%s' 2>/dev/null
# Uncommitted changes count
git -C {repo} status --porcelain | wc -l
# Current branch
git -C {repo} branch --show-current
Guard every substitution (|| echo "?") — freshly-cloned repos with an
unborn HEAD exit 128 on log/rev-parse and must not abort the sweep.
3. Generate Activity Report
Create a sorted table showing:
| Repository | Last Commit | Age | Branch | Uncommitted |
|---|---|---|---|---|
| repo-name | commit msg | 2d | main | 3 files |
Sort by most recent activity first.
4. Highlight Active Projects
Flag repositories with:
- Commits in the last 7 days
- Uncommitted changes
- Non-main/master branches (active development)
Output Format
## Active Repositories (last 7 days)
| Repository | Last Activity | Branch | Status |
|------------|---------------|--------|--------|
## Recently Active (7-30 days)
| Repository | Last Activity | Branch | Status |
|------------|---------------|--------|--------|
## Dormant (>30 days)
| Repository | Last Activity |
|------------|---------------|
## Summary
- X repositories scanned
- Y active in last 7 days
- Z with uncommitted 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.
- 7d ago First seen · 102 lines · 65 tokens per session scan A 14a0f88fbfae
repo-activity is a skill published in the GitHub repository laurigates/dotfiles (10 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 780 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-31.
Other skills, from other repositories
work-on
End-to-end workflow for shipping a GitHub issue. Assesses complexity, builds a tailored workflow, and orchestrates skills from research through PR.
checkout
Start work on a new issue or feature by creating a jj change on the up-to-date default branch with an optional named bookmark.
advanced-jj
Reference for deeper Jujutsu (jj) topics beyond the everyday describe/advance workflow. Load when working with conflicts, the operation log, bookmarks, revsets, fork/PR workflows, colocated Git repos, multi-remote setups, divergent changes, or jj config. Also the place to look up fileset glob syntax, non-interactive…
pr
Create a draft or ready pull request with gh for a jj revision — pushes the bookmark, reviews the full changeset, and drafts a title and body explaining why the change was made. Use when asked to open a PR.
commit
Describe and finalize work with jj-vcs — drafting a description for the current change, splitting mixed work into focused commits, and advancing to a clean working copy. Use when asked to commit, when finishing a unit of work, or when starting new work on top of undescribed changes.
github-repository
Configure a GitHub repository's description, homepage, topics, and solo-developer settings via gh, derived from the codebase. Use when tidying repo settings.