A research workflow for investigating a question using multiple sources and producing a cited Markdown report under docs/research/.

Use it for general research, market or competitor analysis, and technology selection when comparing tools, libraries, frameworks, software kits, or repositories.

It separates short lookups from deeper investigations and provides evidence that readers can check.

research — Skill for Claude Code and Codex by int2t05

Install

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.

Any agent

npx skills add int2t05/engineering-skills --skill research

Clone the repo

git clone --depth 1 https://github.com/int2t05/engineering-skills

Made for: Claude Code, Codex.

Or install engineering-skills, the plugin that ships this one along with the rest of its 47 skills, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/int2t05/engineering-skills/research/github.svg)](https://agentmods.dev/skills/int2t05/engineering-skills/research)

Your own site

<a href="https://agentmods.dev/skills/int2t05/engineering-skills/research"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/research/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/int2t05/engineering-skills/research"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 518 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.00518
Opus 5.5	$0.00010	$0.00207
Sonnet 5.5	$0.00005	$0.00104
Haiku 4.5	$0.00003	$0.00052

Measured 15d ago against content hash bee42ca626bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research 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 15d 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.

skills/02-research/research/SKILL.md · 41 lines

How it starts

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

Research

When to use

Investigate a question using verifiable sources and comparable criteria.

Not for: design-research for visuals; spec for requirements.

Steps

Agree the question, decision, coverage and output path; choose general, market or tech-selection mode.
Read primary documentation and relevant real repository files. Record source, commit and implementation evidence; report unavailable community sources.
Compare candidates on the same requirements. Separate facts, inference and uncertainty; failed searches do not prove absence.
Lead with usefulness, applicability and recommendation, then evidence and limits. Explain what additional evidence could change the decision.

Output: Suggested paths, subject to human audit: docs/research/YYYY-MM-DD-<slug>.md, docs/research/market.md or docs/research/competitor.md; prefer its existing owner.

Verify

Claims trace to retrieved evidence; candidates share criteria and missing coverage is explicit.

References

engineering-principles.md — shared decision boundaries, scope and verification.
human-audit.md — document consent, readability and human review.
product-principles.md — product discipline (the real competitor is the current workaround). Linked by market + tech-selection modes.
references/report-spine.md — reader-first organization, evidence, diagram selection and human review.
references/general-mode.md — question framing, primary sources and bounded synthesis.
references/market-mode.md — problem, alternatives, sizing and distribution evidence with selection-bias limits.
references/tech-selection-mode.md — actual constraints, implementation evidence and comparable selection criteria.
references/web-tool-fallback.md — when a fetch tool is blocked or quota-exhausted: tiered fallback by quota dependency (GitHub → indexed docs → scrape → discovery), orthogonal to page-level retries.
references/pressure-scenarios.md — behavioral scenarios for certainty, access gaps, popularity and report bloat.

Read the full file on GitHub · 41 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

15d ago Changed · -97 lines · +26 tokens per session bee42ca626bb
21d ago Changed · +1 lines c5ba3c37e767
2mo ago First seen · 137 lines · 0 tokens per session scan A 405563e2356c

Subscribe to this mod's changes

research is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 15d ago), licensed MIT. It adds 26 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5.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-31.

Claude Code Code review Research TDD Writing and docs agent-skills claude-code-plugin sdlc

design-reviewer

Use after AC and before RED for any wave that ships UI or changes existing behaviour. Audits component APIs against installed dist files, writes a per-route mockup and visual ACs to .wave/dr.md.

Harshvardhan86/claude-wave-plugin · 46 tokens

test-audit

Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.

QBall-Inc/the-bulwark · 0 tokens

plan

Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.

greglas75/zuvo · 53 tokens

research