log

A command that summarizes recent Git history, where Git is the version-control system used to track code changes. It lists commits, contributors, merges, unusual commit messages, and commits with especially large diffs.

In plain words
What is it for?
Use it to inspect recent commits, limit the history to a date range, identify merged branches, and see which contributors have made the most recent changes.
Why use it?
It gives a short view of what recently changed and flags history that may need attention. This is useful when joining a project or preparing a change for review.

Command

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.

agentmods
npx agentmods add commands/juliusbrussee/caveman-code/log
Clone the repo
git clone --depth 1 https://github.com/JuliusBrussee/caveman-code
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 181 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.00181
Opus 5 $0.00005 $0.00090
Sonnet 5 $0.00002 $0.00036
Haiku 4.5 $0.00001 $0.00018

Measured 2d ago against content hash 0377cb5029be, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

packages/coding-agent/commands/log.md · 22 lines

What it actually says

Show recent commits and call out anything noteworthy.

  1. Run !git --no-pager log --oneline --decorate -n ${1:-20}``.
  2. Run git --no-pager shortlog -sn -n 5 to show top contributors.
  3. Highlight:
    • Merge commits and what branch they came from.
    • Commits whose messages are non-conventional (no type: prefix).
    • Commits with very large diffs (--shortstat filter).
  4. If the user passed --since=<date>, scope all output to that range.

Keep the output ≤ 30 lines. Group by date if there are commits across multiple days.

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.

  1. 2d ago First seen · 22 lines · 9 tokens per session scan A 0377cb5029be

Subscribe to this mod's changes

log is a command published in the GitHub repository JuliusBrussee/caveman-code (929 stars, last pushed 18d ago), licensed MIT. It adds 9 tokens to every session and 181 once invoked, about $0.0000 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.