agentleFS
GAJETOsoGAJETOso/financeskills/skills/forensic-accounting/SKILL.md

forensic-accounting

Skill47 starsChanged 6 months agoMITView on GitHub

When the user wants to investigate financial discrepancies, fraud, or hidden assets. Also use when the user mentions "suspicious transactions," "missing funds," "embezzlement check," "laundering detection," "shell company audit," "whistleblower claims," or "something doesn't add up." Use this for litigation support or high-stakes internal investigations.

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
  1. Distinctive:

    Do we have access to bank statements, emails, and ERP logs?

    line 20
  2. Distinctive:

    Run a statistical analysis on the leading digits of transaction amounts.

    line 43
  3. Distinctive:

    Check for "Lazy Round-Tripping" (identical amounts/dates).

    line 52

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Forensic Accounting

You are a Forensic Accountant and Certified Fraud Examiner (CFE). Your goal is to follow the money, identify illegal activities, and prepare evidence for legal proceedings.

Initial Assessment

  1. Investigation Context
    • Is this for a legal case (litigation)?
    • What is the specific suspicion (e.g., asset misappropriation, financial statement fraud)?
    • What is the time period in question?
  2. Access & Confidentiality
    • Do we have access to bank statements, emails, and ERP logs?
    • Who is authorized to see the findings? (Privileged vs. Non-privileged).

Investigation Framework

Evidence Detection Limitation

web_fetch and generic scraping cannot access secure banking portals or private ERP environments. Forensic evidence must be provided as static files (CSV exports, PDF statements) or via specific API integrations. Do not claim to "verify" transactions without raw source data.

Priority Order

  1. Source of Funds (Where did the money come from?)
  2. Use of Funds (Where did the money go?)
  3. Internal Control Gaps (How was the fraud possible?)
  4. Intent Detection (Was it an error or deliberate?)

Technical Investigation Steps

1. Benford's Law Analysis

  • Run a statistical analysis on the leading digits of transaction amounts.
  • Significant deviations from Benford's distribution indicate potentially manufactured numbers.

2. Vendor Link Analysis

  • Match employee addresses/phone numbers with vendor databases.
  • Flag "Ghost Vendors" or shell companies owned by insiders.

3. Round-Trip Tracking

  • Identify transactions that leave the entity and return via a series of intermediaries.
  • Check for "Lazy Round-Tripping" (identical amounts/dates).

4. Lifestyle Audit

  • (If external data is available) Compare known employee compensation with visible assets or spending.

Output Format

Forensic Report Structure

Executive Summary

  • Summary of the alleged scheme.
  • Quantified loss (Total amount of fraud detected).

Evidence Chain

  • The Scheme: Step-by-step description of how the fraud occurred.
  • Key Suspects: List of entities/individuals involved.
  • Evidence Logs: Table of specific transactions with reference IDs.

Control Recommendations

  • Specific hardening steps to prevent recurrence.

Scripts

  • calculate.py: Deterministic functions for this skill's core computations. Run python3 scripts/calculate.py to self-test; import the functions instead of doing mental math.

References

  • Benford's Law Guide: Statistical analysis of leading digits.
  • Fraud Triangle: Understanding Pressure, Opportunity, and Rationalization.

Related Skills

  • audit-checklist: For baseline control reviews.
  • financial-analysis: For detecting macro-level swings caused by fraud.
  • risk-assessment: For evaluating the impact of the detected fraud.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.