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 skills/postindustria-tech/agentic-toolkit/langgraph-dev-document-processingnpx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-document-processinggit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.00054 | $0.01099 |
| Opus 5 | $0.00027 | $0.00549 |
| Sonnet 5 | $0.00011 | $0.00220 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
document-processing-for-rag 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Processing for RAG
Document processing transforms raw files into chunked, searchable documents for RAG pipelines.
Installation
pip install langchain-community langchain-text-splitters langchain-huggingface faiss-cpu
# Or for GPU support:
pip install faiss-gpu
# For hybrid search (BM25 + semantic):
pip install rank-bm25
Processing Pipeline (Tutorial 03)
Load -> Split -> Embed -> Index
Document Loaders
from langchain_community.document_loaders import (
TextLoader,
DirectoryLoader,
PyPDFLoader
)
# Single text file
loader = TextLoader("document.txt")
docs = loader.load()
# Directory of files
# loader_cls defaults to UnstructuredFileLoader (requires 'unstructured' package)
# TextLoader is simpler and works for plain text files
loader = DirectoryLoader("docs/", glob="*.txt", loader_cls=TextLoader)
docs = loader.load()
# PDF files (requires: pip install pypdf)
loader = PyPDFLoader("document.pdf")
pages = loader.load()
Text Splitters
RecursiveCharacterTextSplitter (Recommended)
from langchain_text_splitters import RecursiveCharacterTextSplitter
splitter = RecursiveCharacterTextSplitter(
chunk_size=1000, # Characters per chunk (default: 4000)
chunk_overlap=200, # Overlap between chunks (default: 200)
length_function=len # Default length function
)
chunks = splitter.split_documents(documents) # 'documents' from loader.load()
Why overlap? Prevents context loss at chunk boundaries.
CharacterTextSplitter (Simple)
from langchain_text_splitters import CharacterTextSplitter
splitter = CharacterTextSplitter(
chunk_size=1000,
chunk_overlap=0,
separator="\n\n" # Split on paragraphs (default)
)
# Usage
chunks = splitter.split_documents(documents)
# Or for raw text:
# text_chunks = splitter.split_text(text)
Chunking Best Practices
Chunk Size Guidelines (in characters with length_function=len):
- Small (200-500): Precise retrieval, may lack context
- Medium (500-1000): Recommended - Balance of precision and context
- Large (1000-2000): More context, less precise
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.
- yesterday First seen · 169 lines · 54 tokens per session scan A f5416e03a171
document-processing-for-rag is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,099 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…