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/almanax-ai/almanax-security-plugin/setupnpx skills add almanax-ai/almanax-security-plugin --skill setupgit clone --depth 1 https://github.com/almanax-ai/almanax-security-pluginWrote 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/almanax-ai/almanax-security-plugin/setup)<a href="https://agentmods.dev/skills/almanax-ai/almanax-security-plugin/setup"><img src="https://agentmods.dev/badge/skills/almanax-ai/almanax-security-plugin/setup.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.1 | $0.00024 | $0.00386 |
| Opus 5 | $0.00012 | $0.00193 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
setup 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 5d 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
Help the user set up Almanax in Claude Code.
Workflow:
- Explain that this plugin connects Claude Code to the hosted Almanax MCP server at
https://mcp.almanax.ai. - If the user does not already have an Almanax API key, direct them to the Almanax web app at
https://app.almanax.ai. - Tell them to sign in, open their organization settings, go to the
Accounttab, and create an API key inAPI keys. - If they want public documentation, point them to
https://docs.almanax.ai. - Tell them to set the key in their shell before starting Claude Code:
export ALMANAX_API_KEY="their_api_key" - If they want the key to persist across terminal sessions, tell them to add the same export line to their shell profile such as
~/.zshrc. - Tell them to restart Claude Code after setting or changing the key so the Almanax MCP server reconnects with the updated credentials.
- After restart, suggest a verification prompt such as
Use Almanax to get my recent security findingsorScan the current commit with Almanax.
Important:
- Never ask the user to paste their API key into chat.
- Never store the API key in repository files.
- If the user reports authentication failures, suggest checking whether the key is expired, whether they copied it correctly, and whether their Almanax organization has API access enabled.
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.
- 5d ago First seen · 28 lines · 24 tokens per session scan A b2882e10c251
setup 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 386 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…