Borrowing it
Nothing to install: this file belongs to ptmrio/autorename-pdf. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ptmrio/autorename-pdf/main/.claude/skills/rename-pdfs/SKILL.mdgit clone --depth 1 https://github.com/ptmrio/autorename-pdfWrote 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.
[](https://agentmods.dev/skills/ptmrio/autorename-pdf/rename-pdfs)<a href="https://agentmods.dev/skills/ptmrio/autorename-pdf/rename-pdfs"><img src="https://agentmods.dev/badge/skills/ptmrio/autorename-pdf/rename-pdfs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ptmrio/autorename-pdf/rename-pdfs"><img src="https://agentmods.dev/badge/skills/ptmrio/autorename-pdf/rename-pdfs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00568 |
| Opus 5 | $0.00015 | $0.00284 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
rename-pdfs 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 11d 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
Rename PDFs (Development / Cross-Platform)
Rename PDF files using autorename-pdf from source. Requires the Python venv to be active.
Workflow
-
Activate the venv before running any commands:
source venv/Scripts/activate # Windows source venv/bin/activate # macOS / Linux -
Always dry-run first to preview changes:
python autorename-pdf.py rename $ARGUMENTS --dry-run --output json -
Review the output — check that company names, dates, and document types look correct.
-
If the user confirms, run without dry-run:
python autorename-pdf.py rename $ARGUMENTS --output json -
Report results — show renamed count, any failures, and new filenames.
Options
Pass these after the path:
--recursiveor-r— process subfolders--provider <name>— override AI provider (openai/anthropic/gemini/xai/ollama)--model <name>— override AI model--vision— force vision mode (send page images to LLM)--text-only— text extraction only, no OCR/vision--ocr— force PaddleOCR
Undo
python autorename-pdf.py undo --output json
Config
python autorename-pdf.py config show --output json
Company Name Harmonization
harmonized-company-names.yaml maps company name variations to standardized names (e.g., "MSFT", "Microsoft Corp." → "Microsoft"). Uses fuzzy matching (Jaro-Winkler) so OCR typos are handled automatically.
If the dry-run output shows inconsistent or wrong company names, suggest the user add mappings:
StandardName:
- "Variation 1"
- "Variation 2"
Notes
- Config file:
config.yamlin project root (never commit — contains API keys) - Company names file:
harmonized-company-names.yamlin project root (copy from.example) - Output format:
YYYYMMDD COMPANY DOCTYPE.pdf - Providers: openai, anthropic, gemini, xai, ollama
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.
- 11d ago First seen · 76 lines · 31 tokens per session scan A 48d60abd5e11
rename-pdfs is a skill published in the GitHub repository ptmrio/autorename-pdf (117 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 568 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-30.
Other skills, from other repositories
wowerpoint
Turn one document into a kawaii NotebookLM slide-deck PDF. Use for "wowerpoint this", "make a deck about ", "turn this report into slides", or any request to render a single document as shareable narrative slides.
geo-proposal
Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo"…
critic-loop
Run the mandatory 3-round CV review loop with the Critico — autonomously, without going through the Capitano. For each round you spawn a FRESH CRITICO-S session (same N as your Scrittore session: SCRITTORE-2 → CRITICO-S2), send PDF + JD, wait for the structured verdict, kill the Critic, correct the CV, regenerate the…
parse-cv
Pre-process a CV/profile file (PDF, DOCX, ODT, RTF) into plain text BEFORE feeding it to the LLM context. Reduces token cost by 5-10x on long CVs and yields more reliable extraction than reading binary PDFs directly via multimodal vision. The Assistente calls this skill on every uploaded document in…
ase-sync-export
Export the SpecBook-based specification (SPEC) into ready-to-consume renderings like HTML, PDF, normalized Markdown, or JSON. Use when the user wants to "export", "render", or "materialize" the specification.
file-download
Download files from websites, save PDFs, and read downloaded content. Trigger when the user asks to: download a file, save a PDF, export a document, fetch a file from a URL, grab a report, download and read a PDF, or save page content as a file.