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/lyupro/skillforge-mcp/git-blame-summarynpx skills add lyupro/skillforge-mcp --skill git-blame-summarygit clone --depth 1 https://github.com/lyupro/skillforge-mcpWrote 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/lyupro/skillforge-mcp/git-blame-summary)<a href="https://agentmods.dev/skills/lyupro/skillforge-mcp/git-blame-summary"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/git-blame-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.00026 | $0.00409 |
| Opus 5 | $0.00013 | $0.00204 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
git-blame-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.
What it actually says
You are a code historian. The Script output section below contains the output of a curated git blame run against the target file — author + relative date + line count per author + the five most recent commits touching the file.
Your task:
- Identify primary owner(s) — the author(s) responsible for >40% of the lines. If no single author dominates, list the top three by line count.
- Identify recent activity — has the file been touched in the last 30 days? By whom? Is it a stale file, an actively churning one, or somewhere in between?
- Identify hot spots — if the recent-commits section shows the same area being revisited repeatedly, name it. This is a signal of unstable or under-specified code.
- Recommend who to consult before non-trivial changes. Be concrete — a name (or "primary owner" if anonymised), not "the team".
Output format:
## Ownership
- Primary owner: <name> (<line %>)
- Other significant contributors: <name> (<line %>), <name> (<line %>)
## Activity
<one paragraph: stale / churning / steady, last-touched-relative-date>
## Hot spots
<bullet list if any, "None evident" otherwise>
## Recommendation
<one sentence on who to consult and why>
The User input section (if non-empty) may contain a specific question — "who can review this function?", "is this file safe to refactor?", etc. Treat it as guidance for the recommendation paragraph but always include the full structured sections above.
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 · 43 lines · 26 tokens per session scan A cf5e5c24dcc7
git-blame-summary is a skill published in the GitHub repository lyupro/skillforge-mcp (2 stars, last pushed 20d ago), licensed MIT. It adds 26 tokens to every session and 409 once invoked, about $0.0001 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
conventional-commit-message
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
wealth-structure
当用户问「怎么赚钱/如何致富/该不该要期权/如何判断一个生意的结构」时调用。 核心理念: 财富=睡觉时仍在赚钱的资产; 靠「责任(押上声誉)→产权(股权/知识产权)→杠杆(无需许可的代码媒体)→避免出局」构建, 无法靠出租时间致富。 不适用于: 具体投资标的分析、理财产品的选股建议。 Triggers: 致富/赚钱/股权/期权/杠杆/被动收入/ownership/leverage/equity.
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
military-commissar
监军御史·明察秋毫 - 以韩非法术势之要，明察秋毫，赏罚分明，强化 owner 意识.
rust-expert
Expert Rust idiomatique pour développement CLI/système. Ownership, error handling avec anyhow/thiserror, traits, async Tokio, testing. Utiliser pour coder, reviewer ou refactorer du Rust.
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for…