What is agent-reach-tech?

A command-line research tool for coding agents that investigates open-source projects, libraries, security vulnerabilities, technical trends, and related web information.

Use it to evaluate or compare open-source software, research CVEs and security advisories, discover alternatives, monitor trends, read technical sites, or search an existing catalogue.

It gives agents a defined workflow for technical research instead of treating every request as a simple web lookup.

agent-reach-tech — Skill for Claude Code and Codex by ggampp

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 ggampp/agent-reach-tech --skill skill

Clone the repo

git clone --depth 1 https://github.com/ggampp/agent-reach-tech

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ggampp/agent-reach-tech/skill/github.svg)](https://agentmods.dev/skills/ggampp/agent-reach-tech/skill)

Your own site

<a href="https://agentmods.dev/skills/ggampp/agent-reach-tech/skill"><img src="https://agentmods.dev/badge/skills/ggampp/agent-reach-tech/skill/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/ggampp/agent-reach-tech/skill"><img src="https://agentmods.dev/badge/skills/ggampp/agent-reach-tech/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,822 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.00112	$0.01822
Opus 5.5	$0.00045	$0.00729
Sonnet 5.5	$0.00022	$0.00364
Haiku 4.5	$0.00011	$0.00182

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

Security

Grade A, and why

agent-reach-tech 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.

skill/SKILL.md · 206 lines

How it starts

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

Agent Reach Tech — Pesquisa Técnica (v1.1)

Quando usar (auto-trigger)

Use esta skill proativamente quando detectar:

Intenção do usuário	Ação imediata
Avaliar lib/repo OSS	`research oss` ou fluxo Avaliar OSS
CVE, vulnerabilidade, exploit	`research cve` ou fluxo Analisar CVE
Descobrir ferramentas/alternativas	`research discover` ou fluxo Descobrir OSS
Tendências, o que está em alta	`research trends` ou fluxo Monitorar
Ler docs/site técnico	`agent-reach-tech web URL`
Verificar se já está no catálogo	`agent-reach-tech catalog search TERM`
Slash command `/research-tech`	`route` → `research` com report

Não usar para: editar código, fetch de URL trivial já respondida, tarefas sem componente de pesquisa externa.

Router automático (v1.1)

agent-reach-tech route "mensagem do usuário" --json

Ou, se MCP agent-reach-tech estiver ativo: tool route_intent.

Pedido do usuário
    ├─ menciona CVE / vulnerabilidade / GHSA?     → research cve CVE-ID
    ├─ "vale a pena" / "adotar" / "avaliar" / lib? → research oss NOME
    ├─ "alternativas" / "descobrir" / "melhor X"?  → research discover AREA
    ├─ "tendências" / "briefing"?                  → research trends
    └─ só uma URL / documentação?                  → web URL

Pesquisa orquestrada (preferir em v1.1)

Um comando agrega múltiplos canais e gera relatório markdown + sugestão Engram:

agent-reach-tech research oss NOME --repo OWNER/REPO --report
agent-reach-tech research cve CVE-2024-1234 --report
agent-reach-tech research discover "task management" --report
agent-reach-tech research trends --report

Sem --report: JSON completo com campo report embutido.

Regras de execução

Sempre executar CLI ou MCP — não simular pesquisa
Route primeiro se intenção ambígua: agent-reach-tech route "..." --json
Catálogo primeiro — catalog search antes de pesquisa externa
Mínimo 2 fontes — ex: GitHub + HN, ou CVE + NVD web
Citar URLs e data em toda conclusão
Veredito explícito — adotar | observar | evitar (com justificativa)
Persistir — se Engram/memoria MCP ativo: mem_save com decisões relevantes

Read the full file on GitHub · 206 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.

1mo ago First seen · 206 lines · 112 tokens per session scan A dfd8912330a9

Subscribe to this mod's changes

agent-reach-tech is a skill published in the GitHub repository ggampp/agent-reach-tech (0 stars, last pushed 3mo ago), licensed MIT. It adds 112 tokens to every session and 1,822 once invoked, about $0.0004 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.

Research Security

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.