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 pvliesdonk/scholar-mcp --skill scholar-workflowgit clone --depth 1 https://github.com/pvliesdonk/scholar-mcpWrote 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/pvliesdonk/scholar-mcp/scholar-workflow)<a href="https://agentmods.dev/skills/pvliesdonk/scholar-mcp/scholar-workflow"><img src="https://agentmods.dev/badge/skills/pvliesdonk/scholar-mcp/scholar-workflow/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/pvliesdonk/scholar-mcp/scholar-workflow"><img src="https://agentmods.dev/badge/skills/pvliesdonk/scholar-mcp/scholar-workflow.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.00042 | $0.02311 |
| Opus 5.5 | $0.00017 | $0.00924 |
| Sonnet 5.5 | $0.00008 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
scholar-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working effectively with scholarly sources
When the user asks about academic literature, prior art, citations, patents, books, or standards, use the scholar-mcp tools as described below. The server covers four source domains: papers, patents, books, and standards. Each domain has its own tools, but they cross-reference naturally — a paper may cite a patent, a patent's NPL section may reference a paper, and a paper with an ISBN is automatically enriched with book metadata.
Choosing the right search entry point
| User intent | Tool | Key parameters |
|---|---|---|
| Find papers on a topic | search_papers |
query, year_start/year_end, fields_of_study, venue, min_citations, sort |
| Look up a specific paper | get_paper |
identifier — DOI, S2 ID, ARXIV:id, ACM:id, PMID:id |
| Find an author's work | get_author |
Numeric S2 author ID for profile, or name string for disambiguation |
| Find patents | search_patents |
query, cpc_classification, applicant, inventor, jurisdiction, date filters |
| Look up a specific patent | get_patent |
patent_number, sections (biblio, claims, description, family, legal, citations) |
| Find books | search_books |
Prefer title/author over query — dedicated indexes give better recall |
| Look up a book by ISBN | get_book |
identifier — ISBN-10, ISBN-13, OL work ID, or edition ID |
| Find a standard | search_standards |
query, optional body filter (NIST, IETF, W3C, ETSI) |
| Normalise a messy citation | resolve_standard_identifier |
raw — e.g. "rfc9000", "nist 800-53", "wcag 2.2" |
| Resolve a mixed list of IDs | batch_resolve |
identifiers — mix of DOIs, S2 IDs, patent numbers, ISBN: prefixed ISBNs |
Domain-sticky traversal: a paper's references mostly point to other papers; a patent's family members are other patents; a standard often cites other standards. Follow the domain naturally — don't switch tools mid-chain unless the data leads you there (e.g. a patent's NPL citations resolve to papers).
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 · 198 lines · 42 tokens per session scan A a71dec7fa269
scholar-workflow is a skill published in the GitHub repository pvliesdonk/scholar-mcp (2 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,311 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
servicenow-cmdb
Auditing the CMDB as a data model: CI class hierarchy, raw relationships, CMDB health scorecards, data quality (duplicates, orphans, staleness, missing fields) and CSDM 5 conformance. Use when the user mentions CMDB health, CMDB audit, data quality, duplicates, orphaned or stale CIs, CI classes, relationships in…
exploring-tables
Exploring any ServiceNow table: schema, field types, sample records, relationships, data patterns, a record's history (work notes, comments, field changes), and what touches a table or field (business rules, client scripts, UI policies, ACLs, script includes). Use when the user mentions tables, schemas, fields, data…
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents, including trend reports. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM…
analyzing-access
Reviewing who holds which ServiceNow roles and explaining access denials. Lists admin and securityadmin holders, roles granted directly instead of through groups, roles left on inactive or long-absent users, and diagnoses 401/403 errors, empty results and missing fields. Joins users, groups and roles through…
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
assessing-change-impact
Assessing what a ServiceNow change request touched and what followed it: affected CIs, other changes on the same CIs in an overlapping window, and incidents on those CIs after the change, without trusting hidden incident-to-change links. Use this skill whenever the user asks whether a change (a CHG number) caused or…