agentmods.dev

technical-research

technical-research is a skill for Claude Code from YuDefine/nuxt-supabase-starter. It costs 83 tokens per session (1,032 once invoked), scanned A, original, MIT.

A research and technology-planning skill for a software change. It produces a research document for the current plan and updates the project's shared record of its technology choices.

In plain words
What is it for?
Use it to compare technical options, record constraints and success conditions, update techstack.md, and pass confirmed technology changes to the change log.
Why use it?
It prevents implementation planning from relying on an outdated technology stack or leaving important technical decisions unresolved. It also identifies questions that need answers before research is complete.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

not rated 45repo changed today A scan 83 tokens original MIT

Good fit Use it to compare technical options, record constraints and success conditions, update techstack.md, and pass confirmed technology changes to the change log.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yudefine/nuxt-supabase-starter/technical-research
View source ↗ YuDefine/nuxt-supabase-starter
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 YuDefine/nuxt-supabase-starter --skill technical-research
Clone the repo
git clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starter

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/technical-research"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/technical-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,032 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.00083 $0.01032
Opus 5 $0.00042 $0.00516
Sonnet 5 $0.00017 $0.00206
Haiku 4.5 $0.00008 $0.00103

Measured today against content hash 6cadb1445559, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

technical-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 today.

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.

template/.claude/skills/technical-research/SKILL.md · 46 lines

How it starts

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

Technical Research

technical-research 同時產出研究過程與技術堆疊真相：research.md 留在 plan package，specs/truth/techstack.md 是整個系統目前唯一 techstack truth。

SOP

Phase 1 -- 對齊 plan 與 techstack truth

  1. READ 讀取使用者需求、呼叫者要求、目標 plan package 的 spec.md、既有 research.md、truth-delta.md、specs/truth/techstack.md 與必要 codebase 邊界。
  2. READ 讀取 templates/research.md、templates/research.example.md、templates/techstack.md 與 templates/techstack.example.md，確認 research 與 techstack 的責任邊界。
  3. READ 讀取 rules/Research輸出定位與spec後接續判準.md，確認 research.md 寫入 plan package、techstack.md 寫入 specs/truth/techstack.md。
  4. READ 讀取 .agents/constitution/CONSTITUTION.md、.agents/constitution/shared.md、.agents/constitution/skills/technical-research/research.md 與 .agents/constitution/skills/technical-research/techstack.md。

Phase 2 -- 收斂研究缺口與 truth 變更風險

  1. READ 讀取 rules/AIxBDD必問問題與起始專案介面澄清判準.md，對過 spec.md、既有 techstack.md 與使用者這輪原話，標出尚未拍板的必問題。
  2. DELEGATE 若 BDD techstack、測試策略、或起始專案下系統有哪些端尚未拍板，呼叫 /clarify；未問完前停止，不進入 Phase 3。
  3. THINK 必問題已拍板後，再從 spec.md 與現有 techstack truth 整理其餘要拍板的核心決策、候選方案、已知限制、比較面向與成功條件。
  4. READ 若需要判斷其餘缺口是否升級 clarify，讀取 rules/Clarify升級門檻與研究提問預算判準.md。
  5. DELEGATE 若其餘缺口會改變決策集合、候選方案、技術邊界，或高影響修改/刪除既有 techstack truth，呼叫 /clarify；未收斂前停止。

Phase 3 -- 產出 research 與更新 techstack truth

  1. READ 需要確認 research 與 techstack 最小必要資訊時，讀取 rules/研究artifact最小必要資訊判準.md 與 rules/techstack-artifact最小必要資訊判準.md。
  2. WRITE 將 decision-driven 研究內容寫入 specs/plans/NNN-<slug>/research.md。
  3. WRITE 依現有 truth 與本輪決策更新 specs/truth/techstack.md，使其代表目前系統完整技術堆疊，不保留「以某 plan 為準」的分散說法。
  4. THINK 將 techstack truth 改動整理為語意單元層級的 ADD / MODIFY / DELETE / NOOP 列。

Phase 4 -- 更新 truth-delta 並交付

  1. DELEGATE 呼叫 /truth-delta，傳入 plan package、truth root、owner /technical-research 與本輪 techstack truth 改動列。
  2. WRITE 向使用者回報 research.md、specs/truth/techstack.md、truth-delta.md、主要技術決策與殘餘風險。

Read the full file on GitHub · 46 lines

Files

What ships with it

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

  1. today Changed · -1 lines 6cadb1445559
  2. yesterday First seen · 47 lines · 83 tokens per session scan A 3a14b2ce5257

Subscribe to this mod's changes

technical-research is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,032 once invoked, about $0.0004 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-10.

Claude CodePlanningResearchTDDai-assistednuxtsupabasetemplate
Related

Other skills, from other repositories

prd-v07-implementation-loop

Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution"…

mattgierhart/PRD-driven-context-engineering · 113 tokens

prd-v07-test-planning

Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases"…

mattgierhart/PRD-driven-context-engineering · 125 tokens

strict-tdd

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

a5c-ai/babysitter · 34 tokens

prd-v04-user-journey-mapping

Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish…

mattgierhart/PRD-driven-context-engineering · 145 tokens

atomic-tdd

Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…

damusix/atomic-claude · 142 tokens

use-tdd

Implement a requested increment with red-green-refactor. Use when the user types /use-tdd.

blockmatic/basilic · 24 tokens