Is XBert configured consistently across your book? Spot inconsistencies, gaps, and drift in one pass.
1 on GitHubby XBert IntelligenceMITupdated 1 month ago
/
Plugin xbert-config-audit from marketplace xbert in XBertIntelligence/XBert-Plugins. Commands read from the repo's manifest — 1 month ago.
What it installs
Skills (1)
config-audit
Run the XBert Config Audit across a Connect tenant — fingerprint per-client XBert rule enablement, segment the book, and surface inconsistencies, gaps and drift with named bulk-normalisation moves. Use when the user asks about XBert configuration consistency, whether rules are set up the same across
Slash commands (1)
/xbert-config-audit:config-audit
Audit XBert configuration consistency across your book — surface inconsistencies, gaps and drift. Produces a Word document.
Shared rendering skills that turn a structured XBert plugin payload into a Word, Excel or PDF working paper saved to your project folder. Install it alongside the XBert review plugins — they hand their findings to it.
Surface every anomaly XBert that fired across the period as a flat ranked list with per-firing verification and recommended action. Checks the Anomaly Review agent is configured with linked XBerts before reviewing. No invented pattern labels, no user attribution, no Journal data.
Deep vulnerability scanning of your own code, run entirely inside your Claude Code session at a chosen effort tier, with every finding challenged before it is reported and the verification tally computed in code. Turns surviving findings into targeted patches, each verified by a panel of agents, that you apply when you choose.
Independent auditing for AI agents, open source. Claude discovers your setup, confirms the cost, and audits your agent against the one question other tools skip: is it doing the job it's supposed to do, given your business rules and org structure? Test any model (Anthropic, OpenAI, Gemini, Azure, Bedrock, …) graded by self, one independent judge, or a cross-vendor panel; each provider is billed to its own account via a key in your settings, never the command line. Results render as an interactive artifact (with a static-report fallback).
Cedar policy enforcement + Ed25519 signed receipts for every Claude Code tool call. First cryptographic governance plugin — decisions are policy-gated before they run and every decision produces a tamper-evident receipt verifiable offline.
1 skill · 2 commands · 2 agents · hooks
wshobson/agents 42,461
Maintain XBert Config Audit?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.