awesome-agv: Skill for Claude Code

.agents/skills/research-methodology/SKILL.md

research-methodology is a skill for Claude Code, Codex from irahardianto/awesome-agv. It costs 29 tokens per session (687 once invoked), scanned A, original, MIT.

A structured method for researching unfamiliar technologies, libraries, APIs, and implementation patterns before coding.

In plain words
What is it for?
Use it to break a technical question into searchable topics, consult documentation, and record findings in a research log.
Why use it?
It reduces the risk of relying on outdated information or missing important edge cases.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is irahardianto/awesome-agv's own configuration. It tells Claude Code and Codex how to work on awesome-agv itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything awesome-agv configures →

Reuse

Borrowing it

Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/skills/research-methodology/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/irahardianto/awesome-agv

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for research-methodology

README.md
[![agentmods](https://agentmods.dev/badge/skills/irahardianto/awesome-agv/research-methodology/github.svg)](https://agentmods.dev/skills/irahardianto/awesome-agv/research-methodology)
Your own site
<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/research-methodology"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/research-methodology/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.

agentmods 80×15 button for research-methodology

Your own site · 80×15
<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/research-methodology"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/research-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 687 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00687
Opus 5 $0.00015 $0.00344
Sonnet 5 $0.00006 $0.00137
Haiku 4.5 $0.00003 $0.00069

Measured 8d ago against content hash e656cd53d1d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

research-methodology 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/research-methodology/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Research Methodology Skill

Ensure code is informed by accurate, up-to-date knowledge — not stale training data.

When to Invoke

  • Before implementing with unfamiliar tech
  • Evaluating library/framework options
  • Architect informing design decisions
  • Builder encountering unknown API/pattern

Process

1. Topic Decomposition

Break into 2-5 keyword searchable topics:

"Task CRUD API with Supabase":
  1. Supabase client library JS/TS
  2. Supabase RLS policies
  3. Supabase real-time subscriptions
  4. PostgreSQL UUID PK patterns
  5. TS type generation from Supabase

2. Multi-Tool Search

Priority Tool Best For
1st Qurio MCP Deep doc search, official docs
2nd Context7/similar MCP Library-specific API refs
3rd Supabase MCP Supabase-specific docs
4th search_web General, blogs, SO
5th read_url_content Deep reading specific pages

Strategy: broad search → find doc page → deep read → search gotchas + edge cases.

3. Document Findings

Path: docs/research_logs/{feature_name}.md

# Research: {Topic}
Date: {date}
Researcher: {agent}

## Topics Investigated
1. {topic} — {tool} — {finding}

## Key Patterns
- {Pattern}: {description + code}

## API Signatures
```{lang}
// Exact API from docs

Gotchas

  • {Gotcha}: {avoidance}

Code Examples

// Working examples from docs

Sources

Training Data Reliance

  • {topic}: Relying on training data. No external verification.

### 4. Training Data Fallback

If no search yields results:
1. Document queries attempted + tools used
2. Explicitly state: "Relying on training data for {topic}. External verification unavailable."
3. Flag for human review
4. If critical, ask user for docs

**Never silently use training data when verification is available.**

### 5. ADRs

If research reveals choice between 2+ approaches, new dependency, or arch change → create ADR via `adr` skill at `docs/decisions/NNNN-short-title.md`. The `adr` skill template produces structured-spec-compatible ADRs with YAML frontmatter and `<!-- decision -->` annotations.

Read the full file on GitHub · 104 lines

Changes

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.

  1. 8d ago First seen · 104 lines · 29 tokens per session scan A e656cd53d1d2

Subscribe to this mod's changes

research-methodology is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 21d ago), licensed MIT. It adds 29 tokens to every session and 687 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-09-03.

Related

Other skills, from other repositories

agenttrace-session-audit

Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.

sickn33/agentic-awesome-skills · 34 tokens

maintaining-windows-health

Hands-on playbook for Windows 11 disk cleanup, dev-machine optimization, and proactive health alerting. Use when the PC is full or slow, when a BSOD / Kernel-Power 41 / crash dump / commit-memory pressure happened, when the user asks to free disk space, audit storage, set up disk/memory alerts, or restore the same…

CodeAlive-AI/ai-driven-development · 191 tokens

prompt-engineering

Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic…

CodeAlive-AI/ai-driven-development · 76 tokens

installing-cli-tools

Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login; set API keys, tokens, or env variables…

CodeAlive-AI/ai-driven-development · 94 tokens

repo-activity-summary

Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…

CodeAlive-AI/ai-driven-development · 70 tokens

fetch-url-as-markdown

Fetch a web page (URL) and return clean Markdown via local trafilatura, with Exa MCP as a fallback for JS-rendered or anti-bot pages. Use when the user asks to read, fetch, scrape, summarize, or quote a URL — prefer this over the built-in WebFetch tool. Don't use for binary files (PDFs, images, archives) or for…

CodeAlive-AI/ai-driven-development · 90 tokens