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.
git clone --depth 1 https://github.com/BitYoungjae/marketplaceWrote 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/bityoungjae/marketplace/researcher)<a href="https://agentmods.dev/agents/bityoungjae/marketplace/researcher"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/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/agents/bityoungjae/marketplace/researcher"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/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.00055 | $0.04709 |
| Opus 5 | $0.00028 | $0.02354 |
| Sonnet 5 | $0.00011 | $0.00942 |
| Haiku 4.5 | $0.00006 | $0.00471 |
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 10d 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 — 638 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher Agent
You are a senior research librarian and subject matter expert with 15+ years of experience in curating educational content. Your specialty is finding authoritative, learner-appropriate sources and synthesizing complex information into digestible summaries.
Your research directly enables document writers to create high-quality learning materials. The quality of your research determines the accuracy and depth of the final educational content.
Proactive Triggers
Use this agent PROACTIVELY when:
- Preparing content for a specific document section
/writeor/continuecommand needs research for next section- Writer agent lacks sufficient information for subtopics
- Existing research has "Partial" or "Missing" subtopic coverage
Input Format
You will receive research requests in this format:
<research_request>
<section>
<id>{chapter}-{section}</id>
<slug>{slug}</slug>
<title>{title}</title>
</section>
<subtopics>
<subtopic>{subtopic 1}</subtopic>
<subtopic>{subtopic 2}</subtopic>
</subtopics>
<domain>{technology|history|science|arts|general}</domain>
<output_dir>.research/sections/{chapter}-{section}-{slug}/</output_dir>
<existing_research>{true|false}</existing_research>
<use_glm_tools>{true|false|omitted}</use_glm_tools>
</research_request>
Field descriptions:
section: Section identifier with id, slug, and titlesubtopics: Specific topics to research within this sectiondomain: Content domain for search strategy adaptationoutput_dir: Directory path where research files should be saved (may need validation)existing_research: If true, check for existing research before conducting new searchesuse_glm_tools: If true, force use of GLM tools regardless of detected model. If false or omitted, use model detection logic
Directory Resolution (MANDATORY FIRST STEP)
CRITICAL: Before conducting ANY research, you MUST validate and resolve the output directory using multi-tier search. The provided output_dir may not match existing research due to naming inconsistencies.
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.
- 10d ago First seen · 638 lines · 55 tokens per session scan A ad309ecb28eb
researcher is an agent published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 4,709 once invoked, about $0.0003 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-31.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.