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.
/plugin marketplace add maxim-ist/elixir-architectnpx agentmods add plugins/maxim-ist/elixir-architect/marketplacegit clone --depth 1 https://github.com/maxim-ist/elixir-architectGrade A, and why
elixir-architect 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 2d 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": "elixir-architect",
"version": "1.0.0",
"owner": {
"name": "maxim-ist",
"email": "[email protected]"
},
"description": "Expert Elixir/OTP system architect for designing production-ready applications with comprehensive documentation, supervision trees, Ash Framework resources, and AI collaboration handoffs",
"author": {
"name": "borag",
"url": "https://github.com/borag"
},
"license": "MIT",
"homepage": "https://github.com/maxim-ist/elixir-architect",
"repository": {
"type": "git",
"url": "https://github.com/maxim-ist/elixir-architect.git"
},
"keywords": [
"elixir",
"phoenix",
"otp",
"architecture",
"ash-framework",
"supervision-tree",
"oban",
"system-design",
"documentation",
"ai-collaboration",
"director-implementor",
"functional-programming",
"genserver",
"ecto",
"multi-app",
"adr",
"tdd",
"dave-thomas"
],
"plugins": [
{
"name": "elixir-architect",
"source": "./skills/elixir-architect"
}
]
}
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.
- 2d ago First seen · 46 lines scan A 46acdcefee23
elixir-architect marketplace is a plugin published in the GitHub repository maxim-ist/elixir-architect (142 stars, last pushed 9mo ago), licensed MIT. 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-30.
Other plugins, from other repositories
tree-sitter-language-pack
Parse and extract code intelligence from 371 programming languages with tree-sitter — structure, imports, symbols, and syntax-aware chunking.
crawlberg
Web crawling and scraping with HTML→Markdown and headless-Chrome fallback.
excessibility
LiveView introspection and accessibility testing skills for Phoenix. Use htmlsnapshot() to capture state at any point, axe-core for WCAG compliance, timeline analysis for debugging.
elixir-lsp
Elixir Language Server integration for Claude Code.
elixir
Paradigm-shifting skills for Elixir, Phoenix, and OTP development.
mix-compile
Run mix compile --warnings-as-errors after editing Elixir files.