Skip to content
HN On Hacker News ↗

One-shot anomaly detection on the command line¶

▲ 13 points • 1 comments • by chrismungall • 1w ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this entire text is AI.

69 %

AI likelihood · overall

AI
0% human-written 100% AI-generated
SEGMENTS · HUMAN 0 of 1
SEGMENTS · AI 0 of 1
WORD COUNT 325
PEAK AI % 69% · §1
Analyzed
Oct 1
backend: pangram/v3.3
Segments scanned
1 windows
avg 325 words each
Distribution
0 / 100%
human / AI fraction
Verdict
AI
Pangram v3.3

Article text · 325 words · 1 segments analyzed

Human AI-generated
§1 Mixed · 69%

jevotron / airports.csv $ jevotron scan airports.csv --guidance "Check airport locations." 01 / PREVIEW See what goes in¶ Inspect chunks, field paths, and exact model requests before making an API call. Preview a file → 02 / SCAN Assess every entry¶ Jev scores selected fields together. Each entry gets the same guidance and optional examples. Choose your fields → 03 / REVIEW Start with the warnings¶ Sort suspicious entries, export CSV, or pipe JSONL into your existing shell workflow. Build a review queue → Small setup. Useful defaults.¶ CSV, YAML, JSON, TOML, text, OBO, and more work out of the box, including gzip files. The format reference covers defaults and format-specific options. Select fields with --field, add a sentence with --guidance, and run. Longer instructions can come from --guidance-file. A local Python config is available when a project needs custom parsing or reusable settings. Unchanged input reuses its assessment. SQLite saves each successful result as it arrives. Reorder a file, change a reporting threshold, or resume a failed run without reassessing unchanged entries. A review aid with visible evidence. Reports retain each field's probabilities, the entry score, source location, and assessment date. The warning score is the highest field anomaly probability; you choose the threshold. Try a complete example¶ Example What you'll do Airports / CSV Find two injected country errors in public data, then compare versions. Inventory / YAML Apply written rules and a chosen exemplar to stock records. Measurement units / OBO Score definitions and repeated synonyms within independent stanzas. Agent traces / JSONL Classify public agent traces and individual steps, then compare with published labels. Agent traces: a measured pilot¶ On a small, length-filtered sample of 24 public traces, jt matched 130 of 163 step-quality labels (79.8%). Harmful-step precision was 89.7%, with 70.3% recall. The example uses original messages and tool definitions, with human labels withheld from the model. Try the trace example → · Read the full analysis and limitations →