text-processing

A text-file processing skill for reading, writing, searching, analyzing, and transforming text. It can also combine files and perform batch operations.

In plain words
What is it for?
Reading files, extracting sections, counting text, searching for patterns, replacing content, and creating or updating text files.
Why use it?
It handles routine file changes and text analysis without requiring you to edit each file manually.

Skill for Claude CodeCodex

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 skills/muhdaliyan/zeer/text-processing
Any agent
npx skills add muhdaliyan/zeer --skill text-processing
Clone the repo
git clone --depth 1 https://github.com/muhdaliyan/zeer

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 486 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.00037 $0.00486
Opus 5 $0.00018 $0.00243
Sonnet 5 $0.00007 $0.00097
Haiku 4.5 $0.00004 $0.00049

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

Security

Grade A, and why

text-processing 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.

The scan reads SKILL.md. This mod also ships 1 executable file (__init__.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/text-processing/SKILL.md · 78 lines

What it actually says

Goal

Enable text processing operations on files, including reading, writing, searching, and transforming text content.

Capabilities

Read Text Files

  • Read entire file contents
  • Display file content to user
  • Extract specific information from files

Write Text Files

  • Create new text files
  • Overwrite existing files
  • Append to existing files

Text Analysis

  • Count lines, words, characters
  • Search for patterns
  • Extract specific sections

Text Transformation

  • Format text content
  • Replace text patterns
  • Combine multiple files

Procedure

  1. Reading Files

    • Use read_file to get file contents
    • Present content to user or analyze it
  2. Writing Files

    • Use create_file for new files
    • Use write_to_file with append=false to overwrite
    • Use write_to_file with append=true to add content
  3. Processing Text

    • Read file content
    • Process/transform in memory
    • Write results back to file
  4. Batch Operations

    • Use list_directory to find files
    • Process each file individually
    • Report results

Examples

User: "Read the contents of README.md" → Use read_file with path="README.md"

User: "Create a file called notes.txt with 'Meeting notes'" → Use create_file with path="notes.txt" and content="Meeting notes"

User: "Append 'New line' to notes.txt" → Use write_to_file with path="notes.txt", content="New line", append=true

User: "Show me all text files in the docs folder" → Use list_directory with path="docs" → Filter results for .txt files

Best Practices

  • Always check if file exists before reading
  • Confirm before overwriting files
  • Use appropriate line endings for the platform
  • Handle encoding properly (UTF-8 default)
  • Provide clear feedback on operations performed
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 78 lines · 37 tokens per session scan A 58c335121271

Subscribe to this mod's changes

text-processing is a skill published in the GitHub repository muhdaliyan/zeer (5 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 486 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens