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 skills/ggampp/agent-reach-tech/skillnpx skills add ggampp/agent-reach-tech --skill skillgit clone --depth 1 https://github.com/ggampp/agent-reach-techWrote 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/ggampp/agent-reach-tech/skill)<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="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.00112 | $0.01822 |
| Opus 5 | $0.00056 | $0.00911 |
| Sonnet 5 | $0.00022 | $0.00364 |
| Haiku 4.5 | $0.00011 | $0.00182 |
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 3d 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 — 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 searchantes 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_savecom decisões relevantes
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.
- 3d ago First seen · 206 lines · 112 tokens per session scan A dfd8912330a9
agent-reach-tech is a skill published in the GitHub repository ggampp/agent-reach-tech (0 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 1,822 once invoked, about $0.0006 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…