agentmods.dev

scan-commit

scan-commit is a skill for Claude Code, Codex from almanax-ai/almanax-security-plugin. It costs 24 tokens per session (408 once invoked), scanned A, original, Apache-2.0.

A workflow for checking a Git commit or commit range for security vulnerabilities using Almanax.

In plain words
What is it for?
It scans commits, waits for scan results, summarizes findings by severity and affected area, and can guide fixes.
Why use it?
It avoids manually reviewing every changed line for security problems and helps organize the results.

Skill for Claude CodeCodex

Part of the almanax-security plugin — 2 skills, 1 MCP server shipped together

not rated 2 5mo ago A scan 24 tokens original Apache-2.0
View the source file almanax-ai/almanax-security-plugin
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 skills/almanax-ai/almanax-security-plugin/scan-commit
Any agent
npx skills add almanax-ai/almanax-security-plugin --skill scan-commit
Clone the repo
git clone --depth 1 https://github.com/almanax-ai/almanax-security-plugin

Made for: Claude Code, Codex.

Or install almanax-security, the plugin that ships this one along with the rest of its 2 skills, 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.

agentmods badge for scan-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/almanax-ai/almanax-security-plugin/scan-commit.svg)](https://agentmods.dev/skills/almanax-ai/almanax-security-plugin/scan-commit)
Your own site
<a href="https://agentmods.dev/skills/almanax-ai/almanax-security-plugin/scan-commit"><img src="https://agentmods.dev/badge/skills/almanax-ai/almanax-security-plugin/scan-commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 408 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.00024 $0.00408
Opus 5 $0.00012 $0.00204
Sonnet 5 $0.00005 $0.00082
Haiku 4.5 $0.00002 $0.00041

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

Security

Grade A, and why

scan-commit 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 3d 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/almanax-security/skills/scan-commit/SKILL.md · 27 lines

What it actually says

Use Almanax to scan a commit diff and work from the resulting findings.

Workflow:

  1. Determine repo_owner, repo_name, and commit_sha from the user request.
  2. If the user asks to scan the current commit or a recent commit range like "last three commits", infer the current repository and HEAD commit from the local git checkout.
  3. If the user provides or clearly implies a range, include base_sha. Treat requests like "last three commits" as one diff scan ending at HEAD, not three separate scans. Ask a follow-up only if the intended range is ambiguous.
  4. If Almanax tools are unavailable or authentication appears broken, switch to onboarding and guide the user through /almanax-security:setup.
  5. Call almanax_scan_commit.
  6. If Almanax returns selection_required=true, prefer a shared organization project when the user asks for the shared org; otherwise ask the user which org or project to use.
  7. Follow next_action exactly. If next_action=poll_status, wait the full recommended_poll_after_seconds before calling almanax_get_scan_status again, and do not busy-poll.
  8. When findings are available, summarize them clearly by severity and affected area.
  9. If the user wants help fixing issues, address the highest severity findings first.

Important:

  • Never ask the user to paste or expose their API key.
  • If the scan fails because the repository is unavailable in Almanax, explain that they may need to connect GitHub or link the repository in Almanax first.
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. 3d ago First seen · 27 lines · 24 tokens per session scan A 333beade5280

Subscribe to this mod's changes

scan-commit is a skill published in the GitHub repository almanax-ai/almanax-security-plugin (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 408 once invoked, about $0.0001 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.

Git and workflowSecurity
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens