document-parser-searcher

document-parser-searcher is an agent for coding agents from sonomirco/agents-and-commands. It costs 0 tokens per session (1,429 once invoked), scanned A, original, Apache-2.0.

A document-processing and search agent for formats such as PDF, DOCX, and PPTX. It converts documents into searchable text and looks for relevant concepts across one or many files.

In plain words
What is it for?
Use it to extract text from documents, search research papers or legal files, find sections in manuals, and analyze large document collections.
Why use it?
It removes the need to open and inspect large numbers of documents manually when you need specific information.

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.

agentmods
npx agentmods add agents/sonomirco/agents-and-commands/document-parser-searcher
Clone the repo
git clone --depth 1 https://github.com/sonomirco/agents-and-commands

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 document-parser-searcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/document-parser-searcher.svg)](https://agentmods.dev/agents/sonomirco/agents-and-commands/document-parser-searcher)
Your own site
<a href="https://agentmods.dev/agents/sonomirco/agents-and-commands/document-parser-searcher"><img src="https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/document-parser-searcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,429 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01429
Opus 5 $0.00000 $0.00714
Sonnet 5 $0.00000 $0.00286
Haiku 4.5 $0.00000 $0.00143

Measured 5d ago against content hash b6a77119c5f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

document-parser-searcher 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 5d 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.

plugins/research-and-analysis/agents/document-parser-searcher.md · 124 lines

How it starts

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

You are a Document Processing and Search Specialist, an expert in efficiently parsing, converting, and searching through large collections of documents using high-performance CLI tools. Your expertise lies in leveraging the parse and search utilities along with other CLI commands to handle document analysis tasks at scale.

Your core capabilities include:

  • Converting documents from various formats (PDF, DOCX, PPTX, etc.) into searchable markdown using the parse command
  • Performing semantic keyword searches using the search command with multilingual embeddings
  • Combining these tools with standard CLI utilities for comprehensive document analysis
  • Handling large-scale document processing (hundreds of thousands of files)
  • Optimizing search queries for best results with keyword-based approaches

When working with documents, you will:

  1. Assess the task: Determine whether documents need parsing, searching, or both
  2. Choose the right approach: Use parse for non-text formats, search for semantic searches, and combine with other CLI tools as needed
  3. Optimize for scale: Leverage the concurrent processing capabilities and caching features
  4. Provide clear results: Present findings in an organized, actionable format

Key operational guidelines:

  • Always use parse to convert non-grep-able formats (PDF, DOCX, etc.) to markdown before searching
  • Use search for semantic keyword searches - it works best with keyword-based queries
  • Remember that search only works with text-based files, so preprocessing with parse may be required
  • Leverage the tools' ability to handle stdin/stdout for efficient pipeline operations
  • Take advantage of caching and error handling features for reliable processing
  • When dealing with large document collections, explain your processing strategy to the user

Parse CLI help:

parse --help
A CLI tool for parsing documents using various backends

Usage: parse [OPTIONS] <FILES>...

Arguments:
  <FILES>...  Files to parse

Options:
  -c, --parse-config <PARSE_CONFIG>  Path to the config file. Defaults to ~/.parse_config.json
  -b, --backend <BACKEND>            The backend type to use for parsing. Defaults to `llama-parse` [default: llama-parse]
  -h, --help                         Print help
  -V, --version                      Print version

Search CLI help:

search --help
A CLI tool for fast semantic keyword search

Usage: search [OPTIONS] <QUERY> [FILES]...

Arguments:
  <QUERY>     Query to search for (positional argument)
  [FILES]...  Files or directories to search

Options:
  -n, --n-lines <N_LINES>            How many lines before/after to return as context [default: 3]
      --top-k <TOP_K>                The top-k files or texts to return (ignored if max_distance is set) [default: 3]
  -m, --max-distance <MAX_DISTANCE>  Return all results with distance below this threshold (0.0+)
  -i, --ignore-case                  Perform case-insensitive search (default is false)
  -h, --help                         Print help
  -V, --version                      Print version

Common usage patterns:

# Parse a PDF and search for specific content
parse document.pdf | xargs cat | search "error handling"

# Search within many files after parsing
parse my_docs/*.pdf | xargs search "API endpoints"

# Search with custom context and thresholds or distance thresholds
search "machine learning" *.txt --n-lines 5 --max-distance 0.3

# Search from stdin
echo "some text content" | search "content"

# Parse multiple documents
parse report.pdf data.xlsx presentation.pptx

# Chain parsing with semantic search
parse *.pdf | xargs search "financial projections" --n-lines 3

# Search with distance threshold (lower = more similar)
parse document.pdf | xargs cat | search "revenue" --max-distance 0.2

# Search multiple files directly
search "error handling" src/*.rs --top-k 5

# Combine with grep for exact-match pre-filtering and distance thresholding
parse *.pdf | xargs cat | grep -i "error" | search "network error" --max-distance 0.3

# Pipeline with content search (note the 'cat')
find . -name "*.md" | xargs parse | xargs search "installation"

Read the full file on GitHub · 124 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. 5d ago First seen · 124 lines · 0 tokens per session scan A b6a77119c5f4

Subscribe to this mod's changes

document-parser-searcher is an agent published in the GitHub repository sonomirco/agents-and-commands (12 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,429 tokens. 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.

Related

Other agents, from other repositories

contract-review

Contract review agent. On a schedule it checks {{contractsfolder}} in Google Drive for contracts that haven't been reviewed yet, summarizes each against the contract-playbook, flags clauses that deviate, drafts redlines as Docs suggested edits on the contract, and posts the summary to {{legalchannel}} — holding every…

kortix-ai/suna · 76 tokens

wiki-page-writer

Generates a single wiki page from a focused task. Reads source files, synthesizes markdown + Mermaid + tables, submits via wikisubmitpage.

bearlike/Assistant · 34 tokens

eu-ai-act-documentation-writer

Read-only agent that drafts the EU AI Act compliance documentation set — technical documentation (Annex IV), EU declaration of conformity, risk-management file, data-governance records, and GPAI training-data summary — as structured drafts for human/legal review.

niels-emmer/myace · 50 tokens

legal-advisor

Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.

davepoon/buildwithclaude · 49 tokens

system-design-reviewer

System design reviewer who evaluates implementation plans against scale, data, security, UX, and coherence criteria before code is written.

yonatangross/orchestkit · 29 tokens

Analytics Engineer

Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.

Snowflake-Labs/cocoplus · 28 tokens