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 oyi77/1ai-skills --skill research-agentgit clone --depth 1 https://github.com/oyi77/1ai-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/skills/oyi77/1ai-skills/research-agent)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/research-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/research-agent/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/oyi77/1ai-skills/research-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/research-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.01214 |
| Opus 5 | $0.00010 | $0.00607 |
| Sonnet 5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
research-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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This agent investigates topics deeply by pulling multiple sources, cross-referencing claims, and separating evidence from assertion. Use it when a decision depends on facts you do not yet have. It returns findings with provenance so you can audit every conclusion.
Research Agent
Quick Reference — see parent for full agent ecosystem.
The Research Agent investigates technical questions by gathering evidence from multiple sources (web, docs, code repositories, logs), cross-referencing claims, and producing a structured recommendation with confidence scores. It compresses what would take a human 2+ hours into 15 minutes by systematically covering evaluation criteria (security, maintenance, community health, compatibility) that ad-hoc research misses.
When Not to Use
- Simple or one-off tasks — if the task is straightforward, direct execution is faster than structured methodology.
- Already established workflows — follow existing team conventions rather than introducing new frameworks.
- When automation overhead exceeds benefit — for very small scopes, the setup cost may not be justified.
Dependencies
- Python 3.8+ or Node.js 18+
- Access to relevant APIs/services for your specific use case
- Basic understanding of the domain concepts
Commands
# Refer to the skill's usage section for specific commands
# Adapt these to your workflow
Key Responsibilities
- Multi-source evidence gathering: Query web search, official docs, GitHub, Stack Overflow, and internal knowledge bases in parallel
- Cross-reference and verify: Compare claims across sources; flag contradictions and stale information
- Structured recommendations: Produce a ranked output with scores, trade-offs, and a clear decision aligned to project context
Code Example
"""Minimal research agent pattern — evaluate a library."""
import json, sys, subprocess
from datetime import datetime
def research_library(name: str, criteria: list[str]) -> dict:
sources = {}
# Gather from multiple sources (simplified — real agent fetches live data)
sources["github"] = {"stars": "28k", "last_commit": "2025-11-01", "issues": 42}
sources["npm"] = {"weekly_downloads": "1.2M", "security_advisories": 0}
sources["security"] = {"audit_status": "passed", "cves_last_year": 0}
# Score against criteria
recommendations = []
score = sum([
3 if sources["github"]["stars"].rstrip("k").isdigit() and int(sources["github"]["stars"].rstrip("k")) > 10 else 0,
2 if sources["npm"]["security_advisories"] == 0 else -2,
2 if sources["security"]["cves_last_year"] == 0 else -3
])
recommendations.append({
"library": name,
"score": min(score, 10),
"stars": sources["github"]["stars"],
"maintained": sources["github"]["last_commit"],
"security": "clean" if sources["security"]["cves_last_year"] == 0 else "has advisories"
})
return {
"query": f"Evaluate {name} for: {', '.join(criteria)}",
"sources_checked": list(sources.keys()),
"recommendations": sorted(recommendations, key=lambda x: x["score"], reverse=True),
"decision": recommendations[0]["library"] if recommendations else None
}
if __name__ == "__main__":
result = research_library(sys.argv[1], sys.argv[2:])
print(json.dumps(result, indent=2))
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.
- 2d ago Changed · +11 lines 6c85c56793ab
- 12d ago First seen · 125 lines · 19 tokens per session scan A 9e1c8db6ef7d
research-agent is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,214 once invoked, about $0.0001 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 skills, from other repositories
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
ctf-misc
Provides miscellaneous CTF challenge techniques for problems that do not cleanly fit the main categories. Use for encoding puzzles, pyjails, bash jails, RF/SDR, DNS oddities, unicode tricks, esoteric languages, QR or audio puzzles, constraint solving, game theory, unusual sandbox escapes, and hybrid logic puzzles.…
agent-payment-x402
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol.
autonomous-agent-harness
Transform Claude Code into a fully autonomous agent system with persistent memory, scheduled operations, computer use, and task queuing. Replaces standalone agent frameworks (Hermes, AutoGPT) by leveraging Claude Code's native crons, dispatch, MCP tools, and memory. Use when the user wants continuous autonomous…
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
ctf-reverse
Provides reverse engineering techniques for CTF challenges. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malware-like loaders, and anti-debug or…