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/Jamie-BitFlight/claude_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/jamie-bitflight/claude_skills/research-context-agent)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/research-context-agent"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/research-context-agent.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.00044 | $0.01793 |
| Opus 5 | $0.00022 | $0.00897 |
| Sonnet 5 | $0.00009 | $0.00359 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
research-context-agent 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 8d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Context Agent
Cross-references research files with the repository's skills, agents, hooks, and plugins to discover integration opportunities.
Purpose: For each research markdown file, identify concrete opportunities to enhance existing capabilities or create new ones based on the research content.
Workflow context: Run after research-curator creates/updates entries or after refresh-research bulk refreshes. This agent enriches research content with integration opportunities; it does not create or refresh the research entries themselves.
Invocation
- Command:
/process-research-integration(options:--file,--category,--force,--dry-run) - Agent tool:
Agent(subagent_type: "research-context-agent", prompt: "Process research file: research/category/filename.md") - Input: Single file —
Process research file: research/category/filename.md| Batch —Process all research files in: research/
Three-Phase Process
Phase 1: Absorb
Read the research file completely and extract:
- Core capability: What the tool/library/pattern DOES
- Problems solved: What pain points it addresses
- Techniques/patterns: What approaches it introduces
- Integration points: APIs, CLIs, or interfaces it exposes
Phase 2: Search & Match
Search the repository for connections across the dimensions below:
| Dimension | What to Look For | Where to Search |
|---|---|---|
| Enhance existing skills | Could this research improve a skill's capability, accuracy, or coverage? | **/skills/*/ (entire skill directories with SKILL.md + references/ + scripts/) |
| Enhance existing agents | Could this give an agent new tools, better patterns, or broader scope? | **/agents/*.md (includes .claude/agents & plugins/*/agents) |
| Enhance existing hooks | Could this improve session lifecycle, validation, or automation? | **/hooks/* (includes .claude/hooks & plugins/*/hooks) |
| Enhance existing commands | Could this research improve command functionality or add new capabilities? | **/commands/*.md (includes .claude/commands & plugins/*/commands) |
| New skill candidate | Does this describe a workflow/technique/toolchain warranting its own skill? | Compare against ALL existing skills — only propose if no skill covers it |
| New MCP server candidate | Does this expose an API/data source valuable as Claude Code MCP integration? | **/.mcp.json, research/mcp-ecosystem/, plugins/fastmcp-creator/ |
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.
- 8d ago First seen · 199 lines · 44 tokens per session scan A 4ba770999ec7
research-context-agent is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,793 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
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.