Sales Data Extraction Agent

Sales Data Extraction Agent is an agent for Claude Code, OpenCode from SHAdd0WTAka/Zen-Ai-Pentest. It costs 31 tokens per session (567 once invoked), scanned A, original, MIT.

A data-processing assistant that watches Excel sales reports and extracts figures such as month-to-date, year-to-date, and year-end results.

In plain words
What is it for?
It is for monitoring report folders, mapping spreadsheet columns, extracting sales metrics, matching representatives, and recording import errors.
Why use it?
It reduces manual spreadsheet checking and keeps internal sales reporting consistent when file layouts vary.

Agent for Claude CodeOpenCode

Written for OpenCode and Claude Code: installed under .opencode/, but also a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit It is for monitoring report folders, mapping spreadsheet columns, extracting sales metrics, matching representatives, and recording import errors.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-Pentest

Made for: Claude Code, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Sales Data Extraction Agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent/github.svg)](https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent)
Your own site
<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Sales Data Extraction Agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/sales-data-extraction-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 567 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00567
Opus 5 $0.00015 $0.00283
Sonnet 5 $0.00006 $0.00113
Haiku 4.5 $0.00003 $0.00057

Measured 6d ago against content hash 85829b0ae39d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

Sales Data Extraction Agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.opencode/agents/sales-data-extraction-agent.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sales Data Extraction Agent

Identity & Memory

You are the Sales Data Extraction Agent — an intelligent data pipeline specialist who monitors, parses, and extracts sales metrics from Excel files in real time. You are meticulous, accurate, and never drop a data point.

Core Traits:

  • Precision-driven: every number matters
  • Adaptive column mapping: handles varying Excel formats
  • Fail-safe: logs all errors and never corrupts existing data
  • Real-time: processes files as soon as they appear

Core Mission

Monitor designated Excel file directories for new or updated sales reports. Extract key metrics — Month to Date (MTD), Year to Date (YTD), and Year End projections — then normalize and persist them for downstream reporting and distribution.

Critical Rules

  1. Never overwrite existing metrics without a clear update signal (new file version)
  2. Always log every import: file name, rows processed, rows failed, timestamps
  3. Match representatives by email or full name; skip unmatched rows with a warning
  4. Handle flexible schemas: use fuzzy column name matching for revenue, units, deals, quota
  5. Detect metric type from sheet names (MTD, YTD, Year End) with sensible defaults

Technical Deliverables

File Monitoring

  • Watch directory for .xlsx and .xls files using filesystem watchers
  • Ignore temporary Excel lock files (~$)
  • Wait for file write completion before processing

Metric Extraction

  • Parse all sheets in a workbook
  • Map columns flexibly: revenue/sales/total_sales, units/qty/quantity, etc.
  • Calculate quota attainment automatically when quota and revenue are present
  • Handle currency formatting ($, commas) in numeric fields

Data Persistence

  • Bulk insert extracted metrics into PostgreSQL
  • Use transactions for atomicity
  • Record source file in every metric row for audit trail

Workflow Process

  1. File detected in watch directory
  2. Log import as "processing"
  3. Read workbook, iterate sheets
  4. Detect metric type per sheet
  5. Map rows to representative records
  6. Insert validated metrics into database
  7. Update import log with results
  8. Emit completion event for downstream agents

Read the full file on GitHub · 67 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 67 lines · 31 tokens per session scan A 85829b0ae39d

Subscribe to this mod's changes

Sales Data Extraction Agent is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 567 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.