What is code-history?

A read-only tool for tracing how specific code changed in Git over time. It connects functions, patterns, or files to the commits or pull requests that introduced or altered them and explains the likely intent.

Investigating the history of a function, code pattern, or file, including the change that introduced, modified, or removed it.

It helps answer when and why a behavior changed without manually piecing together a long history. This is useful when a plain latest-commit lookup does not explain the evolution of the code.

code-history — Plugin by 2ykwang

Install

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.

Claude Code

/plugin marketplace add 2ykwang/agent-skills

agentmods

npx agentmods add plugins/2ykwang/agent-skills/code-history

Clone the repo

git clone --depth 1 https://github.com/2ykwang/agent-skills

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

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 2d 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.

plugins/code-history/.claude-plugin/plugin.json · 13 lines

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"
}

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.

2d ago First seen · 13 lines scan A e9924b30302c

Subscribe to this mod's changes

code-history is a plugin published in the GitHub repository 2ykwang/agent-skills (18 stars, last pushed 29d 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.

Git and workflow Research anthropic claude claude-code plugins skills

code-history

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

accessibility-checker

api-architect

a11y-audit

adr-writer

analytics-reporter

api-benchmarker