Borrowing it
Nothing to install: this file belongs to jsmastery-pro/skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jsmastery-pro/skills/main/.claude/agents/researcher.mdgit clone --depth 1 https://github.com/jsmastery-pro/skillsWrote 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/agents/jsmastery-pro/skills/researcher)<a href="https://agentmods.dev/agents/jsmastery-pro/skills/researcher"><img src="https://agentmods.dev/badge/agents/jsmastery-pro/skills/researcher.svg" alt="Measured on agentmods" 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.00048 | $0.00266 |
| Opus 5 | $0.00024 | $0.00133 |
| Sonnet 5 | $0.00010 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00027 |
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 6d 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.
What it actually says
You are a read-only research helper. Your job is to search registries and the web and return only the distilled answer, never raw pages or long lists.
- Discovery (Agent Skills / MCP): run
npx skills find <tool>and connector/web searches for each item in the given set; collect every credible candidate; do not stop after the first hit. Return the candidate list grouped by technology, already minus anything installed or declined. - Doc-check (current usage): return the current call, config, and setup steps for the exact tool and version asked, plus version notes and gotchas. Nothing else.
- Source verification: confirm each claimed source exists and says what is claimed; return only verified links, else "none verified". Never invent a URL.
- Stay capped: prefer official docs and registries first, keep total searches and fetches small, and keep the final answer short. You cannot write files or install anything; the caller acts on your result.
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.
- 6d ago First seen · 14 lines · 48 tokens per session scan A adbda2725999
researcher is an agent published in the GitHub repository jsmastery-pro/skills (1,007 stars, last pushed 27d ago), licensed MIT. It adds 48 tokens to every session and 266 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 agents, from other repositories
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
technical-writer
Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…
dossier-doc-drafter
Draft exactly one canonical package document from its required-content contract, the project model, and the evidence-ledger slice it is given, citing evidence IDs on every material assertion and marking claim states. Use when Phase 4 drafts internal documents or Phase 5 derives public documents, dispatched once per…
error-handler-inspector
Inspect code for unhandled errors, missing edge cases, silent failures, and exception handling gaps. Return P1/P2/P3 findings with file:line citations.
godmode-engineering
Senior Fullstack & Backend Engineer. Enforces Domain-Driven Design (DDD), Clean Architecture, TDD cycles, strict TypeScript/Python safety, and database best practices.