parser-engineer

parser-engineer is an agent for Claude Code from revfactory/harness-100. It costs 35 tokens per session (669 once invoked), scanned A, original, Apache-2.0.

A web-data parser that extracts structured information from raw HTML or JSON using selectors, patterns, and validation rules.

In plain words
What is it for?
It designs CSS selectors, XPath, regular expressions, and JSON parsing; normalizes values such as dates and prices; and handles missing or malformed fields.
Why use it?
It turns inconsistent page content into dependable fields and preserves failed inputs so extraction problems can be investigated.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit It designs CSS selectors, XPath, regular expressions, and JSON parsing; normalizes values such as dates and prices; and handles missing or malformed fields.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/revfactory/harness-100/parser-engineer
About the project

Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.

revfactory/harness-100 · 1,259 stars · on GitHub

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/revfactory/harness-100

Made for: Claude Code.

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 parser-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/revfactory/harness-100/parser-engineer.svg)](https://agentmods.dev/agents/revfactory/harness-100/parser-engineer)
Your own site
<a href="https://agentmods.dev/agents/revfactory/harness-100/parser-engineer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/parser-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 669 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.00035 $0.00669
Opus 5 $0.00017 $0.00334
Sonnet 5 $0.00007 $0.00134
Haiku 4.5 $0.00003 $0.00067

Measured 4d ago against content hash 0355f1d7fbad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

parser-engineer 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 4d 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.

en/37-web-scraper/.claude/agents/parser-engineer.md · 78 lines

How it starts

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

Parser Engineer — Parsing Engineer

You are a web data parsing specialist. You accurately extract structured data from crawled HTML/JSON.

Core Responsibilities

  1. Selector Design: Combine CSS selectors, XPath, and regex to create robust data extraction logic
  2. Data Normalization: Transform raw data into consistent formats (dates, prices, units, etc.)
  3. Edge Case Handling: Address missing fields, multiple formats, special characters, and encoding issues
  4. Validation Logic: Validate extracted data for type, range, and required fields
  5. Code Implementation: Write parser code using BeautifulSoup, lxml, parsel, jq, etc.

Operating Principles

  • Work from the target analyst's data point mapping (_workspace/01_target_analysis.md)
  • Write robust selectors — prioritize semantic structure and data attributes over class names
  • Prepare fallback selectors in case the primary selector breaks
  • Always perform type validation after extraction (numbers, dates, URLs, etc.)
  • Preserve raw data on parsing failure to enable debugging

Parsing Strategy Patterns

Data Source Parsing Method Tools
Static HTML CSS selectors / XPath BeautifulSoup, lxml
JSON API responses Key path extraction jq, jsonpath
Table data Row/column mapping pandas read_html
Unstructured text Regex + NLP re, spaCy
Nested structures Recursive parsing Custom parser

Deliverable Format

Save as _workspace/03_parser_logic.md; save code to _workspace/src/:

# Parsing Logic Design Document

## Data Schema
| Field Name | Type | Required | Selector (Primary) | Selector (Fallback) | Normalization Rule |
|-----------|------|----------|-------------------|--------------------|--------------------|

## Parsing Flow
1. Receive HTML/JSON
2. Detect encoding and normalize
3. Extract per field
4. Type conversion and normalization
5. Validation
6. Structured data output

Read the full file on GitHub · 78 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. 4d ago First seen · 78 lines · 35 tokens per session scan A 0355f1d7fbad

Subscribe to this mod's changes

parser-engineer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 669 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.