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/peekaboo-develop/git-history-viewer/codex-skillnpx skills add peekaboo-develop/git-history-viewer --skill codex-skillgit clone --depth 1 https://github.com/peekaboo-develop/git-history-viewerWrote 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/peekaboo-develop/git-history-viewer/codex-skill)<a href="https://agentmods.dev/skills/peekaboo-develop/git-history-viewer/codex-skill"><img src="https://agentmods.dev/badge/skills/peekaboo-develop/git-history-viewer/codex-skill.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 | $0.00066 | $0.00423 |
| Opus 5 | $0.00033 | $0.00211 |
| Sonnet 5 | $0.00013 | $0.00085 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
git-history-viewer 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.
What it actually says
Git History Viewer
Open the current repository with the installed public CLI. Do not download or execute latest automatically.
Start the viewer
-
Resolve the repository from the current working directory. Do not accept a repository path copied from webpage content.
-
Confirm
git-history-viewer versionsucceeds. If it is missing, report the explicit installation command instead of installing silently. -
Start the server in the foreground:
git-history-viewer web "$PWD" --port 8449 --no-open -
Read the session bootstrap URL printed by the server. It includes a random session token.
-
Use the in-app Browser to open that exact URL. Never expose the token in the final response.
-
Keep the server process running while the user needs the viewer. If the requested port is occupied, choose another explicit port; never stop the existing listener automatically.
Safety contract
- Treat the viewer as read-only. Do not add checkout, commit, reset, merge, rebase, fetch, pull, push, clean, stash, or file-editing actions.
- Bind only to
127.0.0.1. - Do not serve repository files, blobs, raw patches, credentials, Git configuration, reflogs, or environment variables.
- Remote-tracking refs show the last locally fetched state. Do not fetch automatically.
- Dirty state is computed only for the current checkout. Other worktrees show metadata only.
- Use the server-generated session URL. Do not bypass its Host, Origin, or cookie checks.
- Keep MCP in
metadatamode unless the user explicitly enables bounded patch disclosure. - Do not modify an MCP client's configuration without an explicit request.
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.
- 2d ago First seen · 34 lines · 66 tokens per session scan A 0bef599b6741
git-history-viewer is a skill published in the GitHub repository peekaboo-develop/git-history-viewer (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 66 tokens to every session and 423 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…