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.
git 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/plugins/almanax-ai/almanax-security-plugin/marketplace)<a href="https://agentmods.dev/plugins/almanax-ai/almanax-security-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/almanax-ai/almanax-security-plugin/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
almanax marketplace 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 7d 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
{
"name": "almanax",
"owner": {
"name": "Almanax"
},
"metadata": {
"description": "Official Almanax Claude Code marketplace.",
"version": "1.0.0"
},
"plugins": [
{
"name": "almanax-security",
"source": {
"source": "git-subdir",
"url": "https://github.com/almanax-ai/almanax-security-plugin.git",
"path": "plugins/almanax-security"
},
"description": "Connect Claude Code to Almanax to scan commits and work with security findings.",
"author": {
"name": "Almanax"
},
"homepage": "https://docs.almanax.ai",
"repository": "https://github.com/almanax-ai/almanax-security-plugin",
"license": "Apache-2.0",
"keywords": ["security", "mcp", "vulnerability-management", "code-scanning"],
"category": "security",
"tags": ["security", "mcp", "code-scanning", "vulnerability-management"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 7d ago First seen · 31 lines scan A 6c1e844ec44d
almanax marketplace is a plugin published in the GitHub repository almanax-ai/almanax-security-plugin (2 stars, last pushed 5mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
knowledge-work-plugins marketplace
Plugin marketplace listing 98 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
container
Teaches Claude container's command surface and how it maps to Docker, Lima, Colima, and Podman on macOS.