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 jontsai/claude-plugins --skill researchergit clone --depth 1 https://github.com/jontsai/claude-pluginsWrote 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/jontsai/claude-plugins/researcher)<a href="https://agentmods.dev/skills/jontsai/claude-plugins/researcher"><img src="https://agentmods.dev/badge/skills/jontsai/claude-plugins/researcher/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/jontsai/claude-plugins/researcher"><img src="https://agentmods.dev/badge/skills/jontsai/claude-plugins/researcher.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.00068 | $0.04297 |
| Opus 5.5 | $0.00027 | $0.01719 |
| Sonnet 5.5 | $0.00014 | $0.00859 |
| Haiku 4.5 | $0.00007 | $0.00430 |
Grade A, and why
researcher 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 — 558 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher
Create distinctive, memorable HTML one-pagers that avoid generic "AI slop" aesthetics.
Setup Required
Before using this skill, configure your output directory:
# Add to your shell profile (~/.zshrc or ~/.bashrc)
export RESEARCHER_DIR="$HOME/research"
# Create the directory structure
mkdir -p "$RESEARCHER_DIR/html" "$RESEARCHER_DIR/md" "$RESEARCHER_DIR/pdf"
Requirements:
- macOS, Linux, or Windows with WSL
- Brave Browser or Google Chrome installed
Instructions
When the user asks to research a topic and create a PDF:
-
Research the topic and gather key information
-
Choose an aesthetic preset based on content type (see Document Aesthetics below)
-
Create an HTML file in
$RESEARCHER_DIR/html/with:- Filename:
{topic-slug}-YYYYMMDD.html(lowercase, hyphens, date suffix) - Example:
python-web-frameworks-20251212.html - Date is the creation date; keep original date if updating later
- Compact, print-friendly design (max 1-2 pages)
- Follow the design standards below
- Filename:
-
Generate the PDF by running:
research-pdf-generateOr if the command isn't in PATH:
$RESEARCHER_DIR/generate-pdfs.sh -
Verify the PDF was created in
$RESEARCHER_DIR/pdf/
File Locations
All paths relative to $RESEARCHER_DIR (defaults to ~/research):
| Purpose | Path |
|---|---|
| HTML source files | $RESEARCHER_DIR/html/ |
| Markdown source files | $RESEARCHER_DIR/md/ |
| Generated PDFs | $RESEARCHER_DIR/pdf/ |
| Conversion script | $RESEARCHER_DIR/generate-pdfs.sh |
Output Modes
HTML Mode (Default)
Full-featured output with curated CSS aesthetics. Best for:
- Visually distinctive documents
- Browser viewing with micro-interactions
- Print-quality PDFs
Markdown Mode
Lightweight plaintext output. Best for:
- Version control (git-friendly)
- Easy editing
- Cross-platform compatibility
- Quick notes and drafts
When user requests Markdown output:
- Create file in
$RESEARCHER_DIR/md/{topic-slug}-YYYYMMDD.md - Use clean Markdown formatting (no HTML)
- Include YAML frontmatter for metadata
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 · 558 lines · 68 tokens per session scan A 0ce7ef20f67b
researcher is a skill published in the GitHub repository jontsai/claude-plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 4,297 once invoked, about $0.0003 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
summarize-interview
Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries.
visual-explainer
Generate self-contained HTML pages that visually explain technical material — systems, code changes, plans, data. Use when the user asks for any diagram or visual explanation, when they want a slide deck or a longform document (user guide, how-to, reference page), when another skill needs one rendered, or proactively…
reflect-solution
Summarize WHAT WAS SHIPPED in a Claude Code session as a self-contained HTML slide deck — the elevator pitch (problem, solution, decisions, artifacts, verification, gaps), not a play-by-play of tool calls or debugging detours. Defaults to the current in-context session; optionally accepts a session ID or JSONL path.…
document-parsing
Extraction rules for receipts and invoices. Reference this when processing uploaded receipts or PDF invoices.
docx
This skill should be activated when the user asks to create a Word document, report, memo, letter, proposal, whitepaper, or anything involving .docx output. Also triggers when the user says 'write a report', 'create a document', 'make a Word file', 'draft a proposal', 'generate a whitepaper', or mentions .docx.…
xlsx
This skill should be activated when the user asks to create, edit, read, or analyze Excel spreadsheet files (.xlsx, .xlsm, .csv, .tsv). Triggers for: building financial models, creating data tables, formatting spreadsheets, adding formulas, cleaning tabular data, converting between tabular formats. Also triggers when…