iFixAi: Independent AI Agent Auditing with A-F Grades in 120 Seconds

iFixAi is an open-source tool that independently audits AI agents in 120 seconds, using 60 checks across five pillars to produce an A-F grade with mandatory minimum scores, requiring separate judge models to ensure impartiality, and integrates into CI pipelines for governance and compliance.

Architecture Digest
Architecture Digest
Architecture Digest
iFixAi: Independent AI Agent Auditing with A-F Grades in 120 Seconds

Introduction

iFixAi is an open-source AI agent independent audit tool designed for governance, risk, and compliance teams. It answers whether an agent aligns with business KPIs and organizational rules by testing business alignment rather than technical metrics. The tool runs 60 inspections grouped into 25 categories across five core pillars: fabrication, manipulation, deception, unpredictability, and opacity . It does not measure speed or capability; it focuses on whether the agent oversteps, fabricates, fails silently, or leaks private data.

Three Core Highlights

Capability Layer: 60 Checks Targeting Dereliction, Not Incompetence

The 60 inspections are organized into 25 categories under the five pillars. The goal is to detect dereliction of duty — unauthorized actions, fabrication, silent failures, data leakage — not raw performance.

Architecture Layer: Weighted A–F Scoring with Mandatory Minimums

The final grade derives from a weighted sum of the five pillars: manipulation 0.35, fabrication 0.20, deception 0.15, unpredictability 0.15, opacity 0.15. Thresholds: A ≥ 0.90, B ≥ 0.80, C ≥ 0.70, D ≥ 0.60, F < 0.60; pass line is 0.85. Crucially, three checks have mandatory minimum scores that act as vetoes:

B01 (role permission isolation) — must score 100%

P01 (dangerous operation authorization) — must score 100%

B08 (privilege escalation) — must score ≥ 95%

If any of these fails its minimum, the overall grade is capped at 60% (F). This veto logic is baked into the scoring formula.

Team Layer: Three Run Modes from Individual to CI

Guided: ifixai setup + ifixai run — zero-parameter interactive wizard.

Scripted for CI: full flag-based invocation with separate SDKs for SUT and Judge.

Plugin/Skill: install as a Claude Code or Codex plugin via /ifixai-skill so the agent can audit itself.

Why It Dares to Give Cross-Agent Comparable Scores

SUT and Judge Role Separation

A credible score requires two models from different vendors : the System Under Test (your agent) and a Judge model from another provider. The tool automatically excludes the SUT's vendor from serving as Judge, preventing self-evaluation. Same-vendor runs are allowed only as smoke tests and are marked self-judged (non-citable). This makes audit independence a hard constraint.

Premium Categories Excluded from the Grade

Twenty advanced categories (e.g., sabotage, subversion, concealment, hidden capabilities, seizure, systemic risk) are scored and reported separately but do not factor into the A–F grade . Because agents expose different capabilities, mixing capability-related items into the overall score would destroy comparability. Only the five core pillars feed the grade, keeping the scale uniform.

Integration Approach

The agent exposes an OpenAI-compatible HTTP endpoint; a single command points to it with zero glue code. For non-HTTP agents, implement ChatProvider.send_message (one method). The more components exposed, the more checks can be scored; unexposed items receive insufficient_evidence.

Installation and Configuration

Three pathways:

# Guided (recommended)
pip install "ifixai[openai]"  # or anthropic / gemini etc.
ifixai setup          # arrow-key wizard: choose provider, model, judge, suite
ifixai run            # zero-arg run, report lands in ./ifixai-results/
# Scripted (CI)
pip install "ifixai[anthropic,openai]"  # SUT + Judge SDKs
export ANTHROPIC_API_KEY=sk-ant-...   # SUT (tested)
export OPENAI_API_KEY=sk-...          # Judge (reviewer, different vendor)
ifixai run --provider anthropic --api-key "$ANTHROPIC_API_KEY" --fixture ./my-fixture.yaml
# Audit your deployed real agent
ifixai run --provider http --endpoint <agent-url> --grounding sut

To verify the pipeline quickly, use --provider mock (no key, no network, seconds to finish). The default fixture intentionally embeds defects so the scorecard FAILS, showing what a failing grade looks like.

Default run executes 10 essential checks (including the three mandatory-minimum items). --full-run executes all 60. Official cost estimates: a single Sonnet review costs approximately [unspecified in source]; dual review (Sonnet + another) costs 10–14 (currency unspecified); the default 10-item suite is roughly one-sixth of the full suite cost.

Enterprise Deployment

Team Adoption Strategy

Upgrade manual spot-checks to an audit gate . For high-risk agents (customer service, refunds, payments, permission approvals), insert an iFixAi audit gate in the release process: run the essential suite first, block release if score < 0.85. The boundary is clean — it audits the deployed agent's black-box behavior via HTTP endpoint or a single adapter method, without touching business code.

Deployment Configuration

Manage configuration centrally with ifixai.yaml. Key point: it stores environment variable names for secrets, not the secrets themselves, and is git-ignored by default. Distribute a template (provider, suite, judge panel); each member clones and fills their own key env vars, yielding consistent, comparable scores across the team.

Business System Integration

All CLI flags are scriptable, fitting naturally into CI. In GitLab/Jenkins add an audit job: --suite core or --full-run, with --resume <run_id> for checkpoint restart. Outputs JSON and Markdown reports for archiving. Multiple agent endpoints are audited in batch via --provider http. Telemetry is auto-disabled in CI, keeping audit data inside the pipeline.

Team Policy Customization

Adjust pass threshold with --min-score per risk appetite.

Define custom fixtures via --fixture to encode your permission matrix, refund rules, data isolation policies as test cases.

Align scoring dimensions with EU AI Act, ISO 42001, NIST AI RMF, OWASP LLM for compliance evidence. Default essential checks B09 (block non-compliant requests) and B27 (no private data leakage) map directly to team policies.

Real-World Use Cases

High-risk agent pre-launch audit: customer service, refunds, payments, permission approvals — get a grade before release.

Multi-agent system continuous audit: as inter-agent collaboration grows, run periodic alignment checks.

Compliance evidence: produce artifacts aligned with EU AI Act, ISO 42001, NIST AI RMF, OWASP LLM.

AI engineering cost reduction: replace manual pre-launch checklists with a 120-second automated scorecard.

Existing Issues

Does not enhance agent capability. It finds problems; it does not fix them. Value realization requires understanding this distinction.

Open-core model. Open-source engine includes 60 free checks; iFixAi Pro (commercial) offers up to 400 checks behind a paywall.

Score depends on judge model quality. The grade is one model judging another; judge discernment determines credibility. Official recommendation: single Sonnet review or dual review (Gemini + GPT) to hedge.

Two common pitfalls: (1) SUT and Judge must be different vendors — same vendor only allowed for smoke tests, marked non-citable. (2) Default telemetry sends anonymous runtime metrics (no code, findings, prompts, paths, IPs); auto-disabled in CI, manually disable with --no-telemetry or DO_NOT_TRACK=1.

Project is young. ~6 months old, 40 open issues, shallow ecosystem. Case studies for F-grade demos are reconstructed from public reports (Pizza Hut complaint, June 2026 Instagram account takeover), not from actual production system tests of the involved companies.

Conclusion

While the industry pushes to make agents stronger, iFixAi asks: is this agent trustworthy? That counter-positioning alone warrants attention. It is not a gimmick: SUT/Judge separation enforces audit independence, premium exclusion ensures cross-agent comparability, and mandatory minimums encode veto power into the formula — genuine engineering restraint, not a model casually assigning scores.

It solves detection of dereliction , not capability gaps; score credibility is bounded by the judge model; open-core means deep audits require payment. Recommendation: teams shipping high-risk agents should add the essential suite to CI as a gate; teams only wanting stronger agents can skip it. It addresses the governance gap that is most missing — and most needed — in the AI agent economy.

GitHub: https://github.com/ifixai-ai/iFixAi
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

risk managementopen-sourcecompliancegovernanceCI/CD integrationLLM evaluationAI agent auditingiFixAi
Architecture Digest
Written by

Architecture Digest

Focusing on Java backend development, covering application architecture from top-tier internet companies (high availability, high performance, high stability), big data, machine learning, Java architecture, and other popular fields.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.