evaluation-harness
Skill1 starsChanged 3 months agoMITView on GitHub
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Nikoxkx/Agent-Skillstheir own version, first seen Jun 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Nikoxkx/Agent-Skills★ 1same 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 repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Start with run-skill-test to test a specific skill against its fixtures.
- Very specific: line 14
Run generate-matrix periodically to get a full health dashboard.
- Very specific: line 15
Run benchmark-runner to compare performance before/after skill changes.
- Distinctive: line 26
Every test run has timestamp, skill version, fixture version.
- Distinctive: line 30
Keep eval fixtures and run outputs local-only and gitignored, and redact any auth headers, session cookies, or tokens that a fixture or …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Evaluation Harness
Overview
Lab fixture framework for validating bug bounty skills. Each fixture is a minimal vulnerable-by-design application that a fat skill must detect. Every fixture has a positive control (must detect) and a negative control (must not fire). Skills become measurable: precision, recall, false-positive rate, evidence completeness, runtime. The quality gate for all skill improvements.
Quick Reference
- Skill:
evaluation-harness - Severity range:
info - Required tools:
python3,jq,docker,curl - Expected input files: none
Workflow Selection
- Start with
run-skill-testto test a specific skill against its fixtures. - Run
generate-matrixperiodically to get a full health dashboard. - Run
benchmark-runnerto compare performance before/after skill changes. - Runbooks: use
runbooks/.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
run-skill-test | Test a specific skill against its lab fixtures. | .claude/skills/evaluation-harness/scripts/run_skill_test.py | $OUTDIR/recon/eval/results_manifest.json | $OUTDIR/recon/eval/evidence/ |
generate-matrix | Generate a full evaluation matrix across all skills and fixtures. | .claude/skills/evaluation-harness/scripts/generate_matrix.py | $OUTDIR/recon/eval/eval_matrix.json | $OUTDIR/recon/eval/evidence/ |
benchmark-runner | Run benchmark comparing current skill performance to previous baseline. | .claude/skills/evaluation-harness/scripts/benchmark_runner.py | $OUTDIR/recon/eval/benchmark.json | $OUTDIR/recon/eval/evidence/ |
Evidence Required
- Every test run has timestamp, skill version, fixture version.
- Positive control must trigger detection.
- Negative control must not trigger detection.
- Evidence completeness is scored per fixture.
- Keep eval fixtures and run outputs local-only and gitignored, and redact any auth headers, session cookies, or tokens that a fixture or skill response may embed so they are never committed.
References
- Source of truth:
skill.yaml - Runbooks:
runbooks/ - Inspired by OpenAI Evals, UK AISI Inspect, OWASP testing guides
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.

