agentsclimarketplace

Anomaly detection

Skill yogeshg665/sleuth-fraud-investigator/skills/anomaly-detection

Sleuth - Agent Skills that automate payment fraud investigations, plus a deterministic Python engine as the executable reference. Explainable, deterministic scoring and decisions with tokenized card references and human-review gates.

Install
npx -y skills add yogeshg665/sleuth-fraud-investigator --skill anomaly-detection

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Flags transaction amounts that are statistical outliers relative to the account's own spending history using a z-score. WHEN: "detect anomaly", "statistical outlier", "unusual spend for this account", "amount anomaly", "z-score check", "deviation from normal".

SKILL.md

1.9 KB, 353 tokens by cl100k_base, as published. Nobody here has run it

Anomaly Detection

Overview

Compares the transaction amount to the account's historical spend distribution. Amounts that are several standard deviations above the account mean are flagged as outliers. Accounts with insufficient history are skipped to avoid noise.

When to Use

  • During the detection phase, when the account has enough history to be reliable.

Inputs

InputRequiredDescription
transaction.amountyesThe amount under review.
account_historyyesAt least five prior transactions for the account.

Process

  1. Collect prior amounts for the account. If there are fewer than five, stop.
  2. Compute the mean and population standard deviation. If the deviation is zero, stop, because no meaningful outlier can be defined.
  3. Compute the z-score of the current amount.
  4. If the z-score meets or exceeds zscore_threshold, emit an amount_outlier signal with the z-score and account mean as evidence.

Outputs

Zero or one RiskSignal.

Reference Implementation

src/fraud_investigator/skills/anomaly_detection.py.

Rationalizations

ExcuseRebuttal
"Two prior transactions are enough."Small samples produce unstable z-scores; require a minimum history.
"A high amount is always fraud."Outlier status is relative to the account, not absolute; let scoring decide.

Red Flags

  • A z-score is computed on a zero-variance history.
  • The minimum-history guard is removed.

Verification

  • A clear outlier with adequate history yields a signal whose z-score exceeds the threshold.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.