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 CodeInfinity1/Stram --skill research-paper-searchgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/research-paper-search)<a href="https://agentmods.dev/skills/codeinfinity1/stram/research-paper-search"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/research-paper-search/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/codeinfinity1/stram/research-paper-search"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/research-paper-search.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.00027 | $0.00491 |
| Opus 5.5 | $0.00011 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
research-paper-search 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Paper Search
Purpose
Help build literature sets and understand papers from evidence. Current search uses native web/research tools unless a dedicated scholarly API adapter is implemented.
When To Use
Use for arXiv-style searches, paper lists, related work, literature reviews, methods comparison, and reading provided paper links/PDFs.
Inputs And Evidence
- Topic, constraints, date range, venues, authors, links, PDFs, and output format.
- Source URLs, titles, abstracts, and citation metadata.
Tool Map
research_webpagesfetch_webpagerss_feed_readread_pdfsummarize_pdfsliterature_set_createliterature_set_inspectcitation_bibliography_createweb-data-extractionwrite_note
Workflow
- Define search question and inclusion criteria.
- Use current web evidence for changing paper lists.
- Extract title, authors, venue/date, abstract, link, source references, evidence level, and relevance.
- Read/summarize PDFs when provided and accessible.
- Use
literature_set_createto preserve papers, themes, gaps, limitations, and source references as an inspectable artifact. - Use
literature_set_inspectand optionallycitation_bibliography_createbefore reporting or drafting a literature note.
Native Implementation Boundaries
- Do not import external reference arXiv or external reference academic plugins.
- Add scholarly API adapters natively when needed.
- Avoid fabricating citations.
- Literature-set artifacts are local evidence organization, not proof of live scholarly search by themselves.
Safety And Approval
- Respect copyright and do not reproduce long paper text.
- Distinguish abstract-level review from full-paper reading.
- Mark uncertain metadata.
Verification
- Cite source URLs and dates where possible.
- Confirm PDF extraction succeeded before summarizing details.
- Inspect literature-set artifacts for paper/theme/gap counts.
- Note search limitations.
Failure Modes
- Hallucinating paper titles.
- Missing recent work due to stale knowledge.
- Overstating findings from abstracts alone.
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 · 72 lines · 27 tokens per session scan A 6e02a74708ff
research-paper-search is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 491 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-03.
Other skills, from other repositories
thinking-scientific-method
When a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.
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.
causal-design
Design or audit the identification strategy for an observational study. Use when the task concerns estimands, causal assumptions, threats to identification, or defensible research design rather than model implementation.
pipeline-manifest
Build a traceability manifest linking analysis scripts to inputs, outputs, and manuscript figures or tables. Use when documenting a computational pipeline or locating the source of a reported artefact. Not for verifying that paper claims match code outputs; use the code-paper auditor.
synthetic-data
Generate structurally realistic synthetic datasets for pipeline prototyping, test coverage, or prospective power analysis. Use when code or design must be exercised before real data are available or accessible. Never substitute synthetic records for governed raw data.
latex-diff
Compare two LaTeX files, project directories, or Git revisions and produce human-readable plus machine-readable severity-graded semantic changes. Use when determining what changed between manuscript versions or preparing a revision audit bundle. Not for proofreading one version; use $proofread.