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.
git clone --depth 1 https://github.com/2ykwang/agent-skillsWrote 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/plugins/2ykwang/agent-skills/code-history)<a href="https://agentmods.dev/plugins/2ykwang/agent-skills/code-history"><img src="https://agentmods.dev/badge/plugins/2ykwang/agent-skills/code-history/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/plugins/2ykwang/agent-skills/code-history"><img src="https://agentmods.dev/badge/plugins/2ykwang/agent-skills/code-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-history 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.
What it actually says
{
"name": "code-history",
"version": "0.0.2",
"description": "Trace the git history of specific code \u2014 when a function, pattern, or file was added, modified, or removed, and the intent behind each change. Use when the user asks when or why a piece of code changed, wants the evolution of a function, or needs the commit or PR that introduced a behavior. Read-only; not for plain git log or a single line's last author.",
"author": {
"name": "2ykwang",
"url": "https://github.com/2ykwang"
},
"repository": "https://github.com/2ykwang/agent-skills",
"homepage": "https://github.com/2ykwang/agent-skills/tree/main/skills/code-history",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 82 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 13 lines scan A e9924b30302c
code-history is a plugin published in the GitHub repository 2ykwang/agent-skills (19 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
code-contribution-analysis
Skills for analyzing GitHub pull requests and issues in depth. Fetches contribution data from GitHub and researches architectural context via chunkhound-integration. Standalone useful for code review, and designed to be consumable by Claude Agent SDK applications.
contributor-writing
Writing skills for Shopware core contributors: Architecture Decision Records, PR descriptions (trunk and feature-branch formats), commit messages, and RELEASEINFO/UPGRADE entries. Analyzes branch diffs, classifies changes, and writes content calibrated to change magnitude.
changelog-gen
Generate changelogs from git history with conventional commit parsing.
changelog-writer
Detailed changelog authoring from git history and PRs.
commit-commands
Advanced commit workflows with smart staging and push automation.
create-worktrees
Git worktree management for parallel development workflows.