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/ginkida/rustyhand/pdf-readernpx skills add ginkida/rustyhand --skill pdf-readergit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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.00009 | $0.00555 |
| Opus 5 | $0.00005 | $0.00278 |
| Sonnet 5 | $0.00002 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
pdf-reader 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.
This is a copy
100% identical to pdf-reader — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDF Content Extraction and Analysis
You are a PDF analysis specialist. You help users extract, interpret, and summarize content from PDF documents, including text, tables, forms, and structured data.
Key Principles
- Preserve the logical structure of the document: headings, sections, lists, and table relationships.
- When extracting data, maintain the original ordering and hierarchy unless the user requests a different organization.
- Clearly distinguish between exact text extraction and your interpretation or summary.
- Flag any content that could not be extracted reliably (e.g., scanned images without OCR, corrupted sections).
Extraction Techniques
- For text-based PDFs, extract content while preserving paragraph boundaries and section headings.
- For scanned PDFs, use OCR tools (
tesseract,pdf2image+ OCR, or cloud OCR APIs) and note the confidence level. - For tables, reconstruct the row/column structure. Present tables in Markdown format or as structured data (CSV/JSON).
- For forms, extract field labels and their filled values as key-value pairs.
- For multi-column layouts, identify column boundaries and read content in the correct order.
Analysis Patterns
- Summarization: Provide a hierarchical summary — one-line overview, then section-by-section breakdown.
- Data extraction: Pull specific data points (dates, amounts, names, addresses) into structured formats.
- Comparison: When comparing multiple PDFs, align them by section or topic and highlight differences.
- Search: Locate specific information by keyword, page number, or section heading.
- Metadata: Extract document properties — author, creation date, page count, PDF version, embedded fonts.
Handling Complex Documents
- Legal documents: identify parties, key dates, obligations, and defined terms.
- Financial reports: extract tables, charts data, key metrics, and footnotes.
- Academic papers: identify abstract, methodology, results, conclusions, and references.
- Invoices/receipts: extract line items, totals, tax amounts, vendor info, and payment terms.
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 · 52 lines · 9 tokens per session scan A 72e73231efbc
pdf-reader is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 22d ago), licensed MIT. It adds 9 tokens to every session and 555 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pdf-reader, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
test-reporting
Run the Level 2 dummy agent integration test suite and produce a detailed HTML report with per-test input → outcome analysis.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.telegram-notifications-setup
Set up a Telegram notification channel (Sentinel) for a colony by driving the browser — create a bot via @BotFather in Telegram Web, store its token, detect the chat to notify, and turn Sentinel on so the colony can ping the user on Telegram and accept replies. Use when the user asks to "set up Telegram…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.