dev-research

dev-research is a skill for Claude Code, Codex from Enakoneschniy/claude-dev-stack. It costs 177 tokens per session (1,390 once invoked), scanned A, original, MIT.

A research workflow that uses NotebookLM, a tool for asking questions about a selected collection of documents, to answer development questions with citations.

In plain words
What is it for?
Use it to research frameworks and tools such as Payload or Next.js, compare technology stacks, query project documentation, and search previous session notes.
Why use it?
It helps avoid relying on memory when checking specific documentation or decisions recorded in past development sessions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is notebooklm download mind-map ./vault/research/COMPARISON.json.

Good fit Use it to research frameworks and tools such as Payload or Next.js, compare technology stacks, query project documentation, and search previous session notes.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Enakoneschniy/claude-dev-stack
agentmods
npx agentmods add skills/enakoneschniy/claude-dev-stack/dev-research

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 dev-research

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

agentmods 80×15 button for dev-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/enakoneschniy/claude-dev-stack/dev-research"><img src="https://agentmods.dev/badge/skills/enakoneschniy/claude-dev-stack/dev-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 177 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,390 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00177 $0.01390
Opus 5.5 $0.00071 $0.00556
Sonnet 5.5 $0.00035 $0.00278
Haiku 4.5 $0.00018 $0.00139

Measured 1mo ago against content hash 2f0253e243f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dev-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 1mo 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/dev-research/SKILL.md · 195 lines

How it starts

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

Dev Research Skill

Integrates NotebookLM into development workflow for grounded, citation-backed research. Uses notebooklm-py CLI for all NotebookLM interactions.

Prerequisites

# Check if notebooklm-py is installed
which notebooklm || echo "Install: pip install 'notebooklm-py[browser]'"

# Check auth
notebooklm auth check --test

Notebooks Convention

Each dev notebook follows naming: [Project] — [Purpose]

Examples:

  • "Crypto Portal — Stack Docs" (Payload CMS, Next.js docs)
  • "AI News Portal — CMS Research" (comparing CMS options)
  • "Dev Sessions Archive" (all session logs for cross-project search)

Commands

/research TOPIC

Research a topic using NotebookLM's grounded answers.

# Check if relevant notebook exists
notebooklm list 2>/dev/null | grep -i "TOPIC"

# If not, create one
notebooklm create "Research — TOPIC"
notebooklm use <notebook_id>

# Add sources — user provides URLs, or we search
notebooklm source add "URL1"
notebooklm source add "URL2"
notebooklm source add "./local-doc.md"

# Ask questions
notebooklm ask --json "QUESTION"

Parse JSON response and extract:

  • Answer text
  • Citations with source references
  • Confidence indicators

/docs-query QUESTION

Query project documentation notebook.

# Use the project's docs notebook
notebooklm use <project-docs-notebook-id>
notebooklm ask --json "QUESTION"

This gives grounded answers from actual documentation, not hallucinations.

/compare OPTION1 vs OPTION2

Create a structured comparison using NotebookLM.

notebooklm create "Comparison — OPTION1 vs OPTION2"
# Add documentation for both options
notebooklm source add "URL_OPTION1_DOCS"
notebooklm source add "URL_OPTION2_DOCS"

# Structured comparison questions
notebooklm ask --json "Compare OPTION1 and OPTION2 for: performance, DX, ecosystem, production readiness"
notebooklm ask --json "What are the main trade-offs between OPTION1 and OPTION2?"
notebooklm ask --json "Which is better for: [specific use case]?"

# Generate mind-map for visual comparison
notebooklm generate mind-map
notebooklm download mind-map ./vault/research/COMPARISON.json

Read the full file on GitHub · 195 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. 1mo ago First seen · 195 lines · 177 tokens per session scan A 2f0253e243f3

Subscribe to this mod's changes

dev-research is a skill published in the GitHub repository Enakoneschniy/claude-dev-stack (5 stars, last pushed 1mo ago), licensed MIT. It adds 177 tokens to every session and 1,390 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

obsidian-bases

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

kepano/obsidian-skills · 63 tokens

obsidian

Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.4.2, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use…

gapmiss/obsidian-plugin-skill · 105 tokens

prd-taskmaster

Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…

anombyte93/prd-taskmaster · 80 tokens

bmad-dev-story

Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".

LarsCowe/bmalph · 40 tokens

bmad-quick-dev

Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]".

LarsCowe/bmalph · 46 tokens

bmad-editorial-review-structure

Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure.

LarsCowe/bmalph · 35 tokens