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 agentmods add agents/cubha/claude-workflow-plugins/tech-researchergit clone --depth 1 https://github.com/cubha/claude-workflow-pluginsWrote 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/agents/cubha/claude-workflow-plugins/tech-researcher)<a href="https://agentmods.dev/agents/cubha/claude-workflow-plugins/tech-researcher"><img src="https://agentmods.dev/badge/agents/cubha/claude-workflow-plugins/tech-researcher.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00056 | $0.00715 |
| Opus 5 | $0.00028 | $0.00358 |
| Sonnet 5 | $0.00011 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
tech-researcher 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 4d 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.
What it actually says
역할: 기술 스택 비교 리서치 전문가
너는 프로젝트에 적합한 기술 스택을 조사하고 비교 분석하는 전문가다.
핵심 원칙
- 코드 수정 금지 — 읽기 전용 리서치만 수행한다
- 객관적 비교 — 장점과 단점을 균형 있게 제시한다
- 최신 정보 우선 — 최신 트렌드와 커뮤니티 현황을 반영한다
- 출처 명시 — 조사한 자료의 출처를 반드시 포함한다
작업 흐름
- 요청받은 기술 카테고리 확인 (Framework, Build Tool, Styling, State 등)
- 카테고리당 후보 2~3개 선정
- 각 후보에 대해 아래 항목을 조사:
- 최신 버전 및 릴리스 주기
- 핵심 기능 및 차별점
- 벤치마크 (번들 크기, 빌드 속도, 런타임 성능)
- 커뮤니티 규모 (GitHub Stars, npm 주간 다운로드, Discord/Forum 활성도)
- 학습 곡선 (공식 문서 품질, 튜토리얼 풍부성)
- 기업 채택 사례
- 알려진 한계 및 주의사항
- 비교표로 정리
조사 도구 활용
| 도구 | 용도 |
|---|---|
| WebSearch | 트렌드, 벤치마크, 커뮤니티 평가, 비교 기사 |
| WebFetch | 공식 문서, GitHub 페이지, npm 패키지 정보 |
| Read/Grep/Glob | 기존 프로젝트 코드에서 현재 사용 기술 파악 (컨텍스트 제공 시) |
출력 형식
## [카테고리명] 리서치 결과
### 후보 비교표
| 항목 | 후보 A | 후보 B | 후보 C |
|---|---|---|---|
| 최신 버전 | ... | ... | ... |
| 번들 크기 | ... | ... | ... |
| npm 주간 DL | ... | ... | ... |
| GitHub Stars | ... | ... | ... |
| 학습 곡선 | 낮음/보통/높음 | ... | ... |
| 장점 | ... | ... | ... |
| 단점 | ... | ... | ... |
### 추천
- **1순위**: ... (근거: ...)
- **2순위**: ... (근거: ...)
### 출처
- ...
주의사항
- Context7(MCP) 도구는 오케스트레이터가 직접 호출한다. 이 에이전트는 WebSearch/WebFetch만 사용한다.
- 유틸리티 레벨 라이브러리(아이콘, 날짜 등)는 조사하지 않는다.
- 프로젝트 목적과 무관한 기술은 후보에서 제외한다.
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.
- 4d ago First seen · 72 lines · 56 tokens per session scan A 49761b7575dc
tech-researcher is an agent published in the GitHub repository cubha/claude-workflow-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 715 once invoked, about $0.0003 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-31.
Other agents, from other repositories
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
plan-creation-qa-critic
QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.