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 aiocean/claude-plugins --skill aio-research-kitgit clone --depth 1 https://github.com/aiocean/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/aiocean/claude-plugins/aio-research-kit)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-research-kit"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-research-kit/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/aiocean/claude-plugins/aio-research-kit"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-research-kit.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.00063 | $0.01052 |
| Opus 5 | $0.00032 | $0.00526 |
| Sonnet 5 | $0.00013 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
aio-research-kit 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Kit Skill
Environment
- research: !
which research 2>/dev/null || echo "NOT INSTALLED" - uv: !
which uv 2>/dev/null || echo "NOT INSTALLED" - python3: !
which python3 2>/dev/null || echo "NOT INSTALLED"
Structured 10-phase research framework via nguyenvanduocit/research-kit.
Step 1: Check Availability
Check if research CLI is installed:
which research
If found → skip to Step 3: Use CLI. If not → proceed to Step 2: Install.
Note: Research Kit is a Python CLI tool, not an MCP server.
Step 2: Install
2a. Install via uv (recommended)
uv tool install research-cli --force --from git+https://github.com/nguyenvanduocit/research-kit.git
2b. Install via pip
pip install git+https://github.com/nguyenvanduocit/research-kit.git
2c. Environment Variables (optional)
For AI-assisted reasoning during research:
# DeepSeek R1 reasoning
export DEEPSEEK_API_KEY="your-deepseek-key"
# OR Gemini reasoning
export GOOGLE_AI_API_KEY="your-google-ai-key"
Step 3: Use CLI
Initialize a Research Project
research init
This creates a structured research directory with the 10-phase template:
- Phase 1: Question Formulation — Define research questions
- Phase 2: Literature Review — Survey existing knowledge
- Phase 3: Hypothesis Formation — Develop testable hypotheses
- Phase 4: Methodology Design — Plan research approach
- Phase 5: Data Collection — Gather evidence
- Phase 6: Data Analysis — Analyze findings
- Phase 7: Interpretation — Draw conclusions
- Phase 8: Validation — Verify results
- Phase 9: Documentation — Write up findings
- Phase 10: Peer Review — External validation
Validate Research Structure
research check
Validates that the research project follows the correct structure and all required sections are present.
How to Conduct Research
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 · 130 lines · 63 tokens per session scan A 11205557669e
aio-research-kit is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 1,052 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-09-03.
Other skills, from other repositories
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…