Almanax setup
Skill almanax-ai/almanax-security-plugin/.agents/skills/almanax-setup
Connect Codex to Almanax and walk the user through getting an API key from the Almanax web app.From its SKILL.md
npx -y skills add almanax-ai/almanax-security-plugin --skill almanax-setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
Help the user set up Almanax in Codex.
Workflow:
-
Explain that Almanax is available through the hosted 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 Codex:
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 want a file-based setup instead of the CLI, tell them Codex stores MCP configuration in
~/.codex/config.tomlor a project-scoped.codex/config.toml, and provide this stanza:[mcp_servers.almanax] url = "https://mcp.almanax.ai" bearer_token_env_var = "ALMANAX_API_KEY" -
After setup, 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.