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/nasrulhazim/claude/dev-summarynpx skills add nasrulhazim/claude --skill dev-summarygit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/dev-summary)<a href="https://agentmods.dev/skills/nasrulhazim/claude/dev-summary"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/dev-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.1 | $0.00161 | $0.01698 |
| Opus 5 | $0.00081 | $0.00849 |
| Sonnet 5 | $0.00032 | $0.00340 |
| Haiku 4.5 | $0.00016 | $0.00170 |
Grade A, and why
dev-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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Summary — Multi-Repo Development Stats & Timeline
Scans git repositories and produces combined development summaries with commit stats, timelines, and optional detailed reports.
Command Reference
| Command | Purpose |
|---|---|
/dev-summary quick |
Quick summary table — dates + commit counts |
/dev-summary detailed |
Detailed report — files, contributors, frequency |
/dev-summary timeline |
HTML timeline dashboard with charts |
/dev-summary quick
Generate a quick combined summary table for one or more repos.
Steps
-
Get repo paths — ask the user for repo paths if not provided. Accept:
- Current directory (default)
- Multiple paths (comma or space separated)
- Glob patterns (e.g.,
~/Projects/2026/*)
-
For each repo, extract:
# First commit date git log --reverse --format="%ai" | head -1 # Latest commit date git log --format="%ai" | head -1 # Total commits git log --oneline | wc -l -
Present combined table:
## Development Summary | Repo | Mula | Latest | Commits | |---|---|---|---| | **repo-name** | DD Mon YYYY | DD Mon YYYY | N | | **TOTAL** | **earliest** | **latest** | **sum** | - **Duration**: N days (N weeks) - **Average**: ~N commits/day across all repos -
Run all repo scans in parallel — use parallel tool calls for each repo to minimize wait time.
Notes
- Repo name is derived from directory name
- Dates formatted as
DD Mon YYYY(e.g.,8 Jan 2026) - Duration calculated from earliest first commit to latest last commit
- Average commits/day = total commits / duration days
/dev-summary detailed
Generate a detailed development report with file counts, contributors, and commit frequency analysis.
Steps
-
Run quick summary first — get base stats from
/dev-summary quick -
For each repo, additionally extract:
# Source file count (excluding vendor/node_modules/.git) find . -not -path './.git/*' -not -path './vendor/*' \ -not -path './node_modules/*' -not -path './dist/*' \ -type f | wc -l # Unique contributors git log --format="%aN <%aE>" | sort -u # Commits per month (last 6 months) git log --format="%Y-%m" | sort | uniq -c | tail -6 # Most active day git log --format="%ai" | cut -d' ' -f1 | sort | uniq -c | sort -rn | head -1 # Language/stack detection (check for key files) # composer.json → PHP/Laravel # package.json → Node/JS # go.mod → Go # Cargo.toml → Rust # pyproject.toml → Python
What ships with it
1 file 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 · 227 lines · 161 tokens per session scan A 0d3630fc3cef
dev-summary is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 3d ago), licensed MIT. It adds 161 tokens to every session and 1,698 once invoked, about $0.0008 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…