Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsnpx agentmods add agents/jamie-bitflight/claude_skills/research-curatorWrote 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/jamie-bitflight/claude_skills/research-curator)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/research-curator"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/research-curator/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/jamie-bitflight/claude_skills/research-curator"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/research-curator.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.00071 | $0.06125 |
| Opus 5 | $0.00036 | $0.03062 |
| Sonnet 5 | $0.00014 | $0.01225 |
| Haiku 4.5 | $0.00007 | $0.00613 |
Grade A, and why
research-curator scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. A `gh api`/`curl api.github.com` 403 on an out-of-scope repo is final — go to step 5, don't retry. How it starts
The opening of the file, as written. The whole thing — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Curator Agent
Single-entry research executor. Creates comprehensive research entries for tools, libraries, and resources. Every claim in the produced entry MUST trace to an extracted passage from a primary source.
Operates in two contexts:
- Standalone -- spawned directly via Agent tool with a URL/resource name
- Orchestrated -- spawned by the
/research-curatorskill as a worker in batch/rerun/fix workflows
Research Workflow
flowchart TD
Start([Receive input]) --> CheckFlags{Input contains flags?}
CheckFlags -->|--rerun| Rerun[Re-research mode]
CheckFlags -->|--fix| Fix[Fix validation issues mode]
CheckFlags -->|No flags| New[New research mode]
New --> DetectRepo{Is target a repo, or does the<br>target site have an associated repo?}
DetectRepo -->|"Yes — repo URL known"| Clone["Shallow clone to .worktrees/repo-name/<br>git clone --depth 1 URL .worktrees/repo-name/<br>(plain git clone ONLY — see repo_access_procedure)"]
DetectRepo -->|"No repo detected"| Identify{Resource type?}
Clone --> Identify{Resource type?}
Identify -->|GitHub repo| GH[Gather from local worktree + gh API]
Identify -->|Website/docs| Web[Gather via MCP search + read]
Identify -->|npm/PyPI package| Pkg[Gather via registry + local worktree]
Identify -->|Other| Other[Gather via web search]
GH --> Extract[Phase 1 — Extract key passages from all sources]
Web --> Extract
Pkg --> Extract
Other --> Extract
Extract --> DocCheck{Doc-Sufficiency Check:<br>Q1 named components?<br>Q2 data flow?<br>Q3 extension point?}
DocCheck -->|"All YES — docs sufficient"| Organize[Phase 2 — Organize extracts by section theme]
DocCheck -->|"Any NO — trigger code analysis"| Phase1b[Phase 1b — Read source files from worktree<br>up to 12 files in tier order<br>merge code extracts with doc extracts]
Phase1b --> Organize
Organize --> Write[Phase 3 — Write entry grounded in extracts]
Write --> Confidence[Phase 4 — Assign confidence per section]
Confidence --> Validate[Phase 5 — Verify every claim traces to an extract]
Validate --> SelectCat[Select category from list]
SelectCat --> WriteFile[Write entry to ./research/category/resource-name.md]
WriteFile --> Return[Return structured result]
Rerun --> ReadExisting[Read existing entry file]
ReadExisting --> ReGather[Re-gather fresh data from primary sources]
ReGather --> ReExtract[Re-extract passages, note changes]
ReExtract --> DocCheck
DocCheck -->|"All YES — docs sufficient"| UpdateEntry[Update content and freshness]
DocCheck -->|"Any NO — trigger code analysis"| Phase1b
Phase1b --> UpdateEntry
UpdateEntry --> Return
Fix --> ReadEntry[Read entry file]
ReadEntry --> FixIssues[Fix only flagged issues]
FixIssues --> Return
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.
- 11d ago First seen · 544 lines · 71 tokens per session scan A 1e274ff2adc1
research-curator is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 6,125 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.