agentmods.dev

almanax-security-plugin: Skill for Codex

.agents/skills/almanax-scan-commit/SKILL.md

almanax-scan-commit is a skill for Codex from almanax-ai/almanax-security-plugin. It costs 28 tokens per session (628 once invoked), scanned B, original, Apache-2.0.

A workflow for using Almanax to scan a Git commit or commit range for security vulnerabilities, then summarize or fix the findings. A commit is a saved set of code changes in Git.

In plain words
What is it for?
Scanning the current commit, a recent range, or the last several commits, then reviewing or addressing reported vulnerabilities.
Why use it?
It provides a defined way to review recent changes for security problems and respond to the scan results.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is almanax-ai/almanax-security-plugin's own configuration. It tells Codex how to work on almanax-security-plugin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything almanax-security-plugin configures →

not rated 2repo 5mo ago B scan 28 tokens original Apache-2.0
View source ↗ almanax-ai/almanax-security-plugin
Reuse

Borrowing it

Nothing to install: this file belongs to almanax-ai/almanax-security-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/almanax-ai/almanax-security-plugin/main/.agents/skills/almanax-scan-commit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/almanax-ai/almanax-security-plugin

Made for: Codex.

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 almanax-scan-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/almanax-ai/almanax-security-plugin/almanax-scan-commit/github.svg)](https://agentmods.dev/skills/almanax-ai/almanax-security-plugin/almanax-scan-commit)
Your own site
<a href="https://agentmods.dev/skills/almanax-ai/almanax-security-plugin/almanax-scan-commit"><img src="https://agentmods.dev/badge/skills/almanax-ai/almanax-security-plugin/almanax-scan-commit/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.

agentmods 80×15 button for almanax-scan-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/almanax-ai/almanax-security-plugin/almanax-scan-commit"><img src="https://agentmods.dev/badge/skills/almanax-ai/almanax-security-plugin/almanax-scan-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 628 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00028 $0.00628
Opus 5 $0.00014 $0.00314
Sonnet 5 $0.00006 $0.00126
Haiku 4.5 $0.00003 $0.00063

Measured 9d ago against content hash 3a1604789b17, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

almanax-scan-commit scanned grade B with 1 finding 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 9d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- If they prefer file-based setup, tell them to add the following to `~/.codex/config.toml` or a project-scoped `.codex/config.toml`:
.agents/skills/almanax-scan-commit/SKILL.md · 43 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, guide the user through setup inline:

    • Explain that Almanax is available through the hosted MCP server at https://mcp.almanax.ai.

    • Direct them to https://app.almanax.ai to create an API key from their organization settings under Account -> API keys.

    • Tell them to set the key in their shell: export ALMANAX_API_KEY="their_api_key"

    • Tell them to add the Almanax MCP server: codex mcp add --url https://mcp.almanax.ai --bearer-token-env-var ALMANAX_API_KEY almanax

    • Tell them to verify the server connection with: codex mcp list

    • If they prefer file-based setup, tell them to add the following to ~/.codex/config.toml or a project-scoped .codex/config.toml:

      [mcp_servers.almanax]
url = "https://mcp.almanax.ai"
bearer_token_env_var = "ALMANAX_API_KEY"

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

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. 9d ago First seen · 43 lines · 28 tokens per session scan B 3a1604789b17

Subscribe to this mod's changes

almanax-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 28 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens