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 skills add Lylll9436/Paper-Polish-Workflow-skill --skill get-papergit clone --depth 1 https://github.com/Lylll9436/Paper-Polish-Workflow-skillWrote 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/lylll9436/paper-polish-workflow-skill/get-paper)<a href="https://agentmods.dev/skills/lylll9436/paper-polish-workflow-skill/get-paper"><img src="https://agentmods.dev/badge/skills/lylll9436/paper-polish-workflow-skill/get-paper/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/lylll9436/paper-polish-workflow-skill/get-paper"><img src="https://agentmods.dev/badge/skills/lylll9436/paper-polish-workflow-skill/get-paper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.01057 |
| Opus 5 | $0.00023 | $0.00528 |
| Sonnet 5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
get-paper 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
This Skill searches Google Scholar using Chrome DevTools MCP tools, presents search results to the user for selection, and retrieves BibTeX entries for selected papers. It automates the manual process of searching Google Scholar, clicking "Cite", and copying BibTeX. This Skill does NOT use Semantic Scholar MCP — it operates entirely through browser automation.
Trigger
Activates when the user asks to:
- Search Google Scholar for a paper
- Get BibTeX from Google Scholar
/get-paper <search query>
Workflow
Step 1: Navigate to Google Scholar
- Call
mcp__chrome-devtools__list_pagesto check browser state. - If no page is open on
scholar.google.com, callmcp__chrome-devtools__navigate_pagetohttps://scholar.google.com. - If already on Google Scholar, reuse the current page.
Step 2: Search
- Take a snapshot to find the search box element.
- Fill the search box with the user's query using
mcp__chrome-devtools__fill. - Click the Search button using
mcp__chrome-devtools__click. - Wait for results with
mcp__chrome-devtools__wait_for(text:["Cited by"]).
Step 3: Present Results
- Take a snapshot of search results.
- Extract the top 5-8 results: title, authors, venue, year, citation count.
- Present them as a numbered list to the user.
- Ask the user which paper(s) to retrieve BibTeX for (support multiple selections).
- If the user's query is an exact title and the first result is a clear match, skip asking and auto-select it.
Step 4: Get BibTeX (for each selected paper)
For each selected paper:
- Click Cite: Click the
Citebutton (haspopup="menu") for the selected result. - Wait for dialog: Wait for
["BibTeX"]text to appear. - Click BibTeX link: Click the
BibTeXlink inside the Cite dialog. - Read BibTeX: Wait for
["@"]to appear on the new page. Take a snapshot and extract the full BibTeX entry text. - Navigate back: Go back to the search results page (
mcp__chrome-devtools__navigate_pagetype=back). - Close dialog if open: If the Cite dialog is still showing, click Cancel.
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 · 111 lines · 47 tokens per session scan A 4b872a4c0dd7
get-paper is a skill published in the GitHub repository Lylll9436/Paper-Polish-Workflow-skill (386 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,057 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…