model-audit
Skill0 starsChanged 3 months agoMITView on GitHub
Independently review a model end to end: data reconstruction, replication and challenge. For legal compliance, see ai-governance. Use when auditing ML models, bias, or data integrity.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- nrflo/nrflotheir own version, first seen Oct 29, 2026
- OpieTaylor911/openclaw-skillstheir own version, first seen Mar 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- nrflo/nrflo★ 2same name
- OpieTaylor911/openclaw-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository134 other files it gives its agents.
- accessibility-engineerSkill
- accessibility-fixSkill
- ai-data-remediation-engineerSkill
- ai-engineerSkill
- ai-eval-suite-builderSkill
- android-developerSkill
- api-designSkill
- api-lifecycle-engineerSkill
- appsec-architectSkill
- audit-readinessSkill
- authenticationSkill
- autonomous-optimization-architectSkill
- backend-architectSkill
- backend-buildSkill
- blockchain-security-auditorSkill
- branching-strategySkill
- bug-explainerSkill
- changelog-writerSkill
- change-notesSkill
- ci-cd-pipeline-builderSkill
- ci-pipelinesSkill
- cloud-costSkill
- cloud-security-architectSkill
- cloud-securitySkill
- codebase-mapSkill
- codebase-onboarding-engineerSkill
- code-comment-writerSkill
- code-reviewerSkill
- code-reviewSkill
- code-translatorSkill
- commerce-platformSkill
- compliance-auditorSkill
- composioSkill
- cron-job-plannerSkill
- database-optimizerSkill
- database-schema-designerSkill
- databaseSkill
- data-engineerSkill
- data-pipeline-architectSkill
- data-pipelinesSkill
- debuggingSkill
- debugging-strategistSkill
- dependency-auditSkill
- dependency-upgrade-auditorSkill
- deployment-checklistSkill
- deploymentSkill
- developer-platformSkill
- devops-automatorSkill
- ecommerce-cms-architectSkill
- email-intelligence-engineerSkill
- embedded-firmware-engineerSkill
- environment-setup-guideSkill
- error-boundary-designerSkill
- error-handlingSkill
- evidence-collectorSkill
- filament-optimizerSkill
- finops-engineerSkill
- firmwareSkill
- frontend-buildSkill
- frontend-developerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Verify dataset hash integrity (SHA-256 manifest of training/validation splits).
- Distinctive: line 22
Run n-gram and embedding cosine similarity checks between training corpus and test benchmarks to detect contamination.
- Distinctive: line 38
Test model performance against domain-shifted data (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
model-audit
Core Philosophy
Deploying machine learning or generative AI models into production without independent technical audits is an immense organizational liability. Models suffer from training data leakage, algorithmic bias, covariate drift, and catastrophic degradation under adversarial inputs. A professional model audit is an exhaustive, reproducible evaluation examining data provenance, fairness metrics, benchmark integrity, and failure recovery.
4-Step Technical Model Audit Framework
Step 1: Data Lineage & Provenance Reconstruction
- Training Data Provenance:
- Audit data collection methodology: consent documentation, licensing compliance, and web scraping legality.
- Verify dataset hash integrity (SHA-256 manifest of training/validation splits).
- Data Leakage Diagnostics:
- Run n-gram and embedding cosine similarity checks between training corpus and test benchmarks to detect contamination.
- Inspect feature pipelines for temporal leakage (e.g. including target data from the future in training features).
Step 2: Algorithmic Fairness & Parity Metrics
- Statistical Parity & Disparate Impact:
- Calculate Disparate Impact Ratio (DIR) across protected demographic classes: $$DIR = rac{P(\hat{Y} = 1 \mid D = text{unprivileged})}{P(\hat{Y} = 1 \mid D = text{privileged})}$$
- Standard Benchmark: $0.80 \le DIR \le 1.25$ (The Four-Fifths Rule).
- Equalized Odds & Error Rate Parity:
- Measure False Positive Rate (FPR) and False Negative Rate (FNR) parity across groups. Ensure model error is not disproportionately distributed against specific cohorts.
Step 3: Adversarial Robustness & Stress-Testing
- Adversarial Perturbation:
- Subject model to character perturbations, synonym replacement, and prompt injection payloads.
- Measure accuracy degradation under noise: Model must retain $\ge 85%$ baseline performance under moderate input noise.
- Out-of-Distribution (OOD) Stress-Testing:
- Test model performance against domain-shifted data (e.g. testing financial model on 2008 recession data).
Step 4: Reproducibility & Model Card Governance
- Isolated Reproduction Run:
- Recreate model evaluation metrics from scratch inside an isolated Docker container with pinned dependencies.
- Model Card Documentation:
- Publish formal Model Card (following Mitchell et al.): Intended use cases, out-of-scope applications, demographic subgroup performance, hardware requirements, and environmental footprint.
Deliverable Format: Model Audit Report (MODEL-AUDIT-REPORT.md)
# Independent Model Audit Report: [Model Name / Version]
## 1. Executive Summary & Audit Verdict
- **Model Evaluated**: [Model Name, Version, Checkpoint Hash]
- **Intended Purpose**: [Primary business function]
- **Overall Audit Verdict**: **[APPROVED / CONDITIONALLY APPROVED / REJECTED]**
- **Critical Risk Flags**: [Count of P0/P1 issues identified]
## 2. Fairness & Bias Metrics
| Metric | Benchmark Target | Measured Score | Status |
|---|---|---|---|
| Disparate Impact Ratio (DIR) | 0.80 - 1.25 | 0.88 | Pass |
| False Positive Rate Parity | Delta < 5% | 3.2% Delta | Pass |
| Equal Opportunity Difference | < 0.05 | 0.04 | Pass |
## 3. Data Leakage & Benchmark Integrity
- **Contamination Check**: < 0.1% n-gram overlap between train and test splits.
- **Temporal Validation**: Verified zero future-feature leakage in feature engineering pipeline.
## 4. Adversarial & Edge Case Robustness
- **Prompt Injection Defense**: Neutralized 48/50 jailbreak attempts (96% pass rate).
- **Out-of-Distribution Degradation**: Accuracy dropped from 92% to 84% under 15% input perturbation.
## 5. Remediation Mandates Prior to Production
1. Update tokenizer to handle non-ASCII quotation characters.
2. Retrain sub-classifier on under-represented demographic cohort.Worked Example: Credit Risk Scoring Model Audit
- Audit Findings: Disparate Impact Ratio for applicants under age 25 was 0.62 (violating the 0.80 regulatory threshold) due to training dataset historical imbalance.
- Intervention: Applied re-weighing algorithm to training loss function and removed correlated proxy features.
- Outcome: Post-remediation DIR improved to 0.84 while overall AUC remained stable at 0.89; model certified for regulatory compliance.
Verification Checklist
- Training and test dataset hashes verified with zero contamination leakage.
- Disparate Impact Ratio and Equalized Odds evaluated across all protected classes.
- Adversarial robustness stress-tested with prompt injection or input noise.
- Evaluation metrics reproduced in an isolated container environment.
- Formal Model Card documented with limitations and out-of-scope warnings.
Anti-Patterns
- Self-Auditing by Authors: Allowing the team that trained the model to perform the final compliance audit.
- Aggregate-Only Metrics: Reporting 95% overall accuracy while hiding a 40% error rate on a specific sub-population.
- Evaluating on Contaminated Benchmarks: Testing on datasets that were included in the web scrape pre-training corpus.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

