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 skills add team-attention/plugins-for-claude-natives --skill dev-scangit clone --depth 1 https://github.com/team-attention/plugins-for-claude-nativesWrote 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/skills/team-attention/plugins-for-claude-natives/dev-scan)<a href="https://agentmods.dev/skills/team-attention/plugins-for-claude-natives/dev-scan"><img src="https://agentmods.dev/badge/skills/team-attention/plugins-for-claude-natives/dev-scan.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.1 | $0.00055 | $0.01628 |
| Opus 5 | $0.00028 | $0.00814 |
| Sonnet 5 | $0.00011 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
dev-scan 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Opinions Scan
여러 개발 커뮤니티에서 특정 주제에 대한 다양한 의견을 수집하여 종합.
Purpose
기술 주제에 대한 다양한 시각을 빠르게 파악:
- 찬반 의견 분포
- 실무자들의 경험담
- 숨겨진 우려사항이나 장점
- 독특하거나 주목할 만한 시각
Data Sources
| Platform | Method |
|---|---|
| Gemini CLI | |
| Hacker News | WebSearch |
| Dev.to | WebSearch |
| Lobsters | WebSearch |
Execution
Step 1: Topic Extraction
사용자 요청에서 핵심 주제 추출.
예시:
- "React 19에 대한 개발자들 반응" →
React 19 - "Bun vs Deno 커뮤니티 의견" →
Bun vs Deno
Step 2: Parallel Search (Single Message, 4 Sources)
Reddit (Gemini CLI - WebFetch blocked):
# 단일 Gemini 호출로 Reddit 검색 (명시적 검색 지시 필수)
gemini -p "Search Reddit for discussions about {TOPIC}. Summarize the main opinions, debates, and insights from developers. Include Reddit post URLs where possible. Focus on: 1) Common opinions 2) Controversies 3) Notable perspectives from experienced developers."
주의사항:
site:reddit.com형식은 작동하지 않음 - Gemini가 검색 쿼리가 아닌 작업 요청으로 해석- 반드시 "Search Reddit for..." 형태로 명시적 검색 지시 필요
- 단일 호출이 병렬 호출보다 안정적 (출력 혼재 방지)
Other Sources (WebSearch, parallel):
WebSearch: "{topic} site:news.ycombinator.com"
WebSearch: "{topic} site:dev.to"
WebSearch: "{topic} site:lobste.rs"
CRITICAL: 4개 검색을 반드시 하나의 메시지에서 병렬로 실행. Gemini는 단일 호출, WebSearch는 3개 병렬.
Step 3: Synthesize & Present
수집된 데이터를 분석하여 의미 있는 인사이트를 도출한다.
3-1. 의견 분류 및 패턴 파악
각 소스에서 수집된 의견들을 다음 기준으로 분류:
- 찬성/긍정: 해당 기술/도구를 지지하는 의견
- 반대/부정: 우려, 비판, 대안 제시
- 중립/조건부: "~한 경우에만", "~와 함께 쓰면" 등의 조건부 의견
- 경험 기반: 실제 프로덕션 사용 경험을 바탕으로 한 의견
3-2. 공통 의견(Consensus) 도출
여러 커뮤니티에서 반복적으로 등장하는 의견을 식별:
- 2개 이상의 소스에서 동일한 포인트가 언급되면 공통 의견으로 분류
- 특히 Reddit과 HN에서 동시에 언급되는 의견은 신뢰도 높음
- 구체적인 수치나 사례가 포함된 의견 우선
- 최소 5개 이상의 공통 의견 도출 목표
3-3. 논쟁점(Controversy) 식별
커뮤니티 간 또는 커뮤니티 내에서 의견이 갈리는 지점 파악:
- 같은 주제에 대해 상반된 의견이 존재하는 경우
- 댓글에서 활발한 토론이 벌어진 스레드
- "depends on...", "but actually..." 등의 반론이 많은 주제
- 최소 3개 이상의 논쟁점 식별 목표
3-4. 주목할 시각(Notable Perspective) 선별
독특하거나 깊이 있는 인사이트 발굴:
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.
- 7d ago First seen · 189 lines · 55 tokens per session scan A 77c793273467
dev-scan is a skill published in the GitHub repository team-attention/plugins-for-claude-natives (823 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,628 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…