A command for improving a project's README, documentation, package metadata, GitHub details, comments, and changelog. It focuses on making the project information clearer and more complete.

Use it to prepare a project for other developers, improve its README, document public code, correct package metadata, or update its changelog.

It removes the work of finding missing documentation, setup instructions, API explanations, packaging details, and release notes by checking these areas together.

How SylphxAI/pdf-reader-mcp configures OpenCode

About the project

pdf-reader-mcp, now named anymd, is a local Rust command-line tool and MCP server that converts documents, web pages, images, audio, and video into Markdown or extracted metadata, so AI agents can read them in a consistent text format. It is intended for local document processing without an API key, and the catalogue entries let coding agents call its conversion and search functions.

SylphxAI/pdf-reader-mcp · 1,042 stars · on GitHub · sylphxai.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to SylphxAI/pdf-reader-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SylphxAI/pdf-reader-mcp/main/.opencode/command/polish.md

Clone the repo

git clone --depth 1 https://github.com/SylphxAI/pdf-reader-mcp

Made for: OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/polish/github.svg)](https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/polish)

Your own site

<a href="https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/polish"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/polish/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sylphxai/pdf-reader-mcp/polish"><img src="https://agentmods.dev/badge/commands/sylphxai/pdf-reader-mcp/polish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 469 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00469
Opus 5.5	$0.00006	$0.00188
Sonnet 5.5	$0.00003	$0.00094
Haiku 4.5	$0.00002	$0.00047

Measured 1mo ago against content hash cd0120a8b30d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

polish 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

polish — 100% identical, 0 lines differ

.opencode/command/polish.md · 89 lines

What it actually says

Polish Project

Make project professional, welcoming, and well-documented.

Scope

README:

Clear project description (what, why, how)
Installation instructions (tested)
Quick start example (copy-paste ready)
Key features (3-5 bullet points)
API overview
Links to full docs
Badges (build status, coverage, version, license)
Contributing guidelines link
License

Documentation:

API reference (all public functions)
Usage examples (common scenarios)
Tutorials (step-by-step guides)
Architecture overview
Troubleshooting guide
FAQ
Migration guides (if applicable)

Code Comments:

JSDoc for public APIs
Complex logic explained (WHY not WHAT)
Non-obvious decisions documented
Examples in comments where helpful

Packaging (package.json):

Accurate description
Relevant keywords (10-15)
Repository URL
Homepage URL
Bug tracker URL
Author info
License
Engines specified
Files field (only ship necessary)

GitHub Metadata:

Topics/tags (10-20 relevant tags)
Description (concise, searchable)
Website URL
Social preview image (if applicable)

Changelog:

Update CHANGELOG.md
Clear version history
Breaking changes highlighted
Migration instructions

Contributing:

CONTRIBUTING.md
Code of conduct
Development setup
Testing guidelines
PR process

Execution

Audit what exists vs what's missing
Update outdated content
Create missing documentation
Test all code examples
Verify all links work
Ensure consistency across docs

Quality Checks

README explains project in <5 min read
New user can get started in <10 min
All examples tested and work
No broken links
Search-friendly keywords
Professional presentation
Beginner-friendly

Report: What was added/updated, coverage improved.

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.

1mo ago First seen · 89 lines · 15 tokens per session scan A cd0120a8b30d

Subscribe to this mod's changes

polish is a command published in the GitHub repository SylphxAI/pdf-reader-mcp (1,042 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 469 once invoked, about $0.0001 per session on Opus 5.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-09-06.

PDF Writing and docs ai-agent ai-tools llm-tool mcp pdf-reader

bib-filter

Filter a LaTeX project's bibliography to the entries actually cited, with Overleaf-source resolution, temporary staging, validation, approval-gated canonical replacement, and compilation. Use before submission or after large revisions.

flonat/flonat-research · 41 tokens

bib-parse

Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.

flonat/flonat-research · 50 tokens

brief-compliance-check

Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.

flonat/flonat-research · 45 tokens

insights-deck

Archive an exported Claude Code insights HTML report and turn it into a timestamped Beamer presentation usable from either client. Use when the insights export is the source artifact for a presentation. Not for a general research talk; use $talk-deck.

flonat/flonat-research · 49 tokens

latex-health-check

Compile all LaTeX projects and report cross-project build consistency. Use when checking whether a collection of papers builds cleanly. Not for rendered visual inspection after a clean build; use $latex-polish.