AI data stopped being sold as answers this year.
We build code and agent tasks that frontier models still fail, and publish the traces.
Six notes on what changed on the buyer's side — and what we measured.
@ziqiao_ma for the public-dataset third-party benches you also reimplement internally — do those BenchBench rows come from your internal runs, or from the vendor's published number?
Give your LLM-as-judge an experience memory. AgentAuditor: no extra training — RAG over curated memory to catch Agent safety + security risks. #AgentAuditor#LLMJudge#AgentSafety#AgentSecurity#RAG
ASSEBench: 2293 labeled agent interactions, strict + lenient dual labels.
How it works: build feature + reasoning memory from past judgments → retrieve context-aware CoT shots → LLM judge. Lifts multiple LLMs toward human annotator agreement on agent risk calls.
TXT/Markdown · JSON/XML/YAML · DB/CSV/Excel — same agent loop. Model + code + training data open. DM for hard agent / eval data that trains stacks like this.
First agentic LLM for data science: DeepAnalyze-8B (Renmin U + Tsinghua). #1 on HF Daily Paper at drop. #DeepAnalyze#AgenticAI#DataScience#LLM#OpenSource#AIResearch
Prep → analysis → modeling → viz → insight. Structured/semi/unstructured data in, analyst-grade report out.
Sparse reward + scarce paths in DS agents. Two levers: Curriculum-based Agentic Training (simple→complex in real envs) and Data-grounded Trajectory Synthesis — 500K reason + env-interact traces.
@omarsar0 been sending agents into raw paper repos — they usually choke on the env, not the method. the best-worst gap falling from 21.6 to 3.9 after refined artifacts feels familiar.
@dbreunig popular benches don't just get overfit — they train a house style into the agent. high-taste evals are how you pick the behavior you actually want.
@PatronusAI 25–50% less filler across 12 models × 20 tasks, and the bill didn't follow. "Need inspect repo. Grep." is a voice change, not a cheaper run.
@loresjpg quick check — after the lowercase-filename tweak, is the grader locked to the new requirement, or can a pass still come from the original DeepSWE tests?
@169Pi_ai 61.2 on SWE-Bench Verified from a 9B on-device card is a big claim — still want the decontam and sampling settings before treating it as settled.