What is commit-context?

A way to trace a piece of code to the commit and agent session that created it. A commit is a saved set of changes in Git, a tool for tracking code history.

Use it to investigate a file, function, or line and report its Git history and linked session details.

It helps explain why code exists when the reason is not clear from the current files alone.

commit-context — Skill for Claude Code by rmarquesa

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.

Any agent

npx skills add rmarquesa/agentmemory-offline --skill commit-context

Clone the repo

git clone --depth 1 https://github.com/rmarquesa/agentmemory-offline

Made for: Claude Code.

Or install agentmemory, the plugin that ships this one along with the rest of its 15 skills, 2 commands, 12 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rmarquesa/agentmemory-offline/commit-context/github.svg)](https://agentmods.dev/skills/rmarquesa/agentmemory-offline/commit-context)

Your own site

<a href="https://agentmods.dev/skills/rmarquesa/agentmemory-offline/commit-context"><img src="https://agentmods.dev/badge/skills/rmarquesa/agentmemory-offline/commit-context/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rmarquesa/agentmemory-offline/commit-context"><img src="https://agentmods.dev/badge/skills/rmarquesa/agentmemory-offline/commit-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 569 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00061	$0.00569
Opus 5.5	$0.00024	$0.00228
Sonnet 5.5	$0.00012	$0.00114
Haiku 4.5	$0.00006	$0.00057

Measured 1mo ago against content hash 11a6e724628c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-context 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.

Origin

This is a copy

100% identical to commit-context — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugin/skills/commit-context/SKILL.md · 65 lines

What it actually says

The user wants commit context for: $ARGUMENTS

Quick start

git blame -L 40,52 src/auth/refresh.ts   # -> SHA 9a1b2c3d

memory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" }

Expected output:

9a1b2c3 on main by dev: "rotate refresh tokens"
Linked session 7f3a9c2 "Auth refresh rework", 14 obs.

Why

Report only what git and the lookup return. When the lookup gives commit: null, the commit predates session linking; do not invent intent.

Workflow

Find the SHA: git blame -L <start>,<end> <file> for a line range; git log -L :<function>:<file> for a function; git log -n 1 -- <file> for a bare path.
Look it up: memory_commit_lookup { "sha": "<full-sha>" }.
Present the commit (sha, short sha, branch, author, message), the linked session(s) (id, project, started/ended, observation count, summary), and the importance >= 7 observations via memory_recall when available.

Anti-patterns

WRONG: lookup returns { "commit": null }, you narrate "the agent was refactoring auth" from the diff alone.

RIGHT: "This commit predates session linking, so there is no recorded agent session. From git show: it changed token rotation in refresh.ts."

Checklist

SHA came from git blame/log, not a guess.
commit: null reported as "predates linking", no fabricated session.
Session details quote the lookup response verbatim.
No intent claimed beyond what observations state.

Troubleshooting

See ../_shared/TROUBLESHOOTING.md if memory_commit_lookup is not available.

Files

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.

EXAMPLES.md 1.6 KB

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.

1mo ago First seen · 65 lines · 61 tokens per session scan A 11a6e724628c

Subscribe to this mod's changes

commit-context is a skill published in the GitHub repository rmarquesa/agentmemory-offline (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 61 tokens to every session and 569 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to commit-context, differing in 2 lines, and is treated as a copy.

Commits Git and workflow agent-memory local-first mcp offline privacy

commit-history

List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.

M-T-D-N/agentmemory-codex-windows · 49 tokens

git-ops

Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.

Prismer-AI/PrismerCloud · 62 tokens

evolve-lite:unpublish

Remove your published entity from a write-scope repository and restore a private copy.

AgentToolkit/altk-evolve · 23 tokens

codex-adapter

Route ONE bounded, mechanical task to the Codex CLI as a non-Claude executor, under the same review-before-merge gate as any other agent-produced diff. Use when the user explicitly asks to hand a task to Codex, or names OpenAI Codex / a non-Claude executor for a mechanical change (rename a symbol across files, add a…

wrg32786/aigent-os · 101 tokens

git-commits-and-prs

Load BEFORE creating a git commit or a GitHub pull request. Step-by-step protocol for drafting commit messages, staging safely, amend rules, and gh pr create choreography.

sergezuber/FABULA-LLM-5 · 42 tokens

cartographer-kb-conflict-resolve

Guide an agent through resolving open git rebase conflicts on degraded KB concepts.

BeppeTemp/cartographer · 24 tokens

commit-context