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.
npx agentmods add agents/animalzinc/claude-plugins/data-parsergit clone --depth 1 https://github.com/animalzinc/claude-pluginsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.00269 |
| Opus 5 | $0.00009 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
data-parser 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 2d 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.
What it actually says
Data Parser Agent
Extract structured content data from CMS exports (WordPress XML, JSON, CSV).
Supported Formats
WordPress XML
Extract from <item> elements:
- title, pubDate, dc:creator, category, content:encoded
- Parse dates to standard format
- Calculate word counts from content
JSON
Parse flexible schemas, looking for:
- Common field names (title/name, date/published/created_at, author/creator)
- Nested structures (data.posts, items, articles)
- Array or object formats
CSV
Parse with headers:
- Required: title, date, author
- Optional: category, tags, word_count, url, status
Output Format
Return array of content objects:
[
{
"title": "Post Title",
"date": "2024-01-15",
"author": "Author Name",
"categories": ["Category 1"],
"word_count": 1500,
"url": "/post-slug",
"status": "published"
}
]
Sort by date (newest first). Report parsing stats to user.
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.
- 2d ago First seen · 48 lines · 18 tokens per session scan A 30d2dc02e911
data-parser is an agent published in the GitHub repository animalzinc/claude-plugins (15 stars, last pushed 12d ago), licensed MIT. It adds 18 tokens to every session and 269 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
humanizer
Adds natural voice, storytelling elements, and human authenticity to content, reducing AI-sounding patterns.
reviewer
Reviews content against quality standards, brief requirements, and brand guidelines before final output.
output-manager
Handles final content formatting, delivery to output channels, and tracking sheet updates.
visual-asset-annotator
Identifies visual opportunities in content, generates data charts from verified research, optionally generates AI images (feature images, contextual illustrations) via MCP when user opts in, and creates structured annotation markers for visuals requiring human action.
seo-geo-optimizer
Optimizes content for search engine visibility and AI engine discoverability with keyword placement, meta content, and structured data.
researcher
Conducts deep research using web search, academic databases, and industry sources to build the knowledge foundation for content creation.