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 ifixai-ai/iFixAinpx agentmods add plugins/ifixai-ai/ifixai/plugingit clone --depth 1 https://github.com/ifixai-ai/iFixAiGrade A, and why
ifixai 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": "ifixai",
"displayName": "iFixAi",
"version": "0.2.0",
"description": "Independent auditing for AI agents, open source. Claude investigates your agent, authors an iFixAi fixture from its setup, and audits it against the one question other tools skip: is it doing the job it's supposed to do, given your business rules and org structure? Adversarial depth, assurance discipline. Test any provider's model (Anthropic, OpenAI, Gemini, Azure, Bedrock, …) as system-under-test and judge, each billed to its own account via a key in your settings.",
"author": {
"name": "iFixAi",
"url": "https://github.com/ifixai-ai/iFixAi"
},
"homepage": "https://github.com/ifixai-ai/iFixAi#readme",
"repository": "https://github.com/ifixai-ai/iFixAi",
"license": "Apache-2.0",
"keywords": ["safety", "diagnostic", "misalignment", "evaluation", "alignment"],
"defaultEnabled": true
}
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 · 16 lines scan A 0310b8d2e3c3
ifixai is a plugin published in the GitHub repository ifixai-ai/iFixAi (11,559 stars, last pushed 3d 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-30.
Other plugins, from other repositories
responsible-ai-skills
Responsible AI skills for coding agents — bias assessment, governance documentation, explainability, fairness testing, and alignment review. Auto-activates when building AI systems.
deep-process-skills
Structured workflows that make LLMs think instead of just respond. Skills for verification, exploration, architecture, risk, feasibility, synthesis, and more.
coder-eval
Test whether your Claude Code skills actually trigger, and benchmark any coding agent — author, run, and analyze the eval suite that proves it, locally or as a CI gate.
ai-sdlc
AI-SDLC governance framework for Claude Code — action enforcement, telemetry, quality gates, and review agents.
martinloop
Govern coding-agent work with budgets, stop conditions, and verifier-backed evidence.
nio
Plugin marketplace listing 1 plugin: nio.