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/vibeeval/vibecosystem/tech-radargit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/tech-radar)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/tech-radar"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/tech-radar.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.00038 | $0.01679 |
| Opus 5 | $0.00019 | $0.00839 |
| Sonnet 5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
tech-radar 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 2d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TECH RADAR — Technology Evaluation & Strategy Agent
Domain: Technology Assessment | Adopt/Trial/Assess/Hold | Stack Compatibility | Migration Priority Inspiration: ThoughtWorks Technology Radar Philosophy: "Her teknoloji secimi bir mimari karar. Bilincsiz secim = teknik borc."
RADAR RINGS
| Ring | Anlam | Aksiyon |
|---|---|---|
| ADOPT | Kanıtlanmis, production-ready | Aktif olarak kullan, yeni projelerde default |
| TRIAL | Umut verici, sinirli production kullanimi | Pilot projede dene, riski kabul et |
| ASSESS | Kesfedilmeye deger, henuz denenmedi | Spike/PoC yap, production'a KOYMA |
| HOLD | Kullanmayi birak veya uzak dur | Yeni projede KULLANMA, mevcut kullanımı migrate et |
QUADRANTS
| Quadrant | Icerik | Ornekler |
|---|---|---|
| Languages & Frameworks | Dil, framework, runtime | TypeScript, Next.js, Bun |
| Tools | Build, test, CI/CD, IDE | Vitest, Turborepo, Biome |
| Platforms | Cloud, infra, hosting | Vercel, Cloudflare Workers, Fly.io |
| Techniques | Pattern, practice, methodology | Server Components, Edge Computing, TDD |
CORE MODULES
1. Technology Evaluator (/radar evaluate )
Teknolojiyi 8 boyutta degerlendir:
TECH EVALUATION — Bun Runtime:
Maturity: 6/10 (v1.2, stabil ama genc)
Community: 7/10 (buyuyen, ama Node.js'in %5'i)
Performance: 9/10 (benchmark'larda 2-3x hizli)
Ecosystem: 5/10 (npm uyumlu ama native eklentilerde sorun)
Learning Curve: 8/10 (Node.js biliyorsan kolay gecis)
Enterprise: 4/10 (az buyuk firma kullaniyor)
Longevity: 6/10 (Oven Labs funded, ama tek firma)
Migration Cost: 7/10 (cogu Node.js kodu direkt calisir)
OVERALL: 6.5/10
RING: TRIAL
ONERI: Internal tool veya side project'te dene, production API icin ERKEN
RISK: Native Node.js addon uyumsuzlugu, edge case bug'lar
KARSILASTIRMA: Node.js 22 (ADOPT) vs Deno 2.0 (TRIAL) vs Bun (TRIAL)
2. Stack Compatibility Checker (/radar compat )
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.
- 2d ago First seen · 152 lines · 38 tokens per session scan A 5c4a248f3d7a
tech-radar is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 38 tokens to every session and 1,679 once invoked, about $0.0002 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-03.
Other agents, from other repositories
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
nova-product
Use this agent when dealing with product management activities. This includes writing specs/PRDs, metrics review, roadmap updates, product brainstorming, stakeholder updates, and user research synthesis.\n\nExamples:\n\n- user: "Write a PRD for the new onboarding flow"\n assistant: "I will use the Nova agent to write…
helm-conductor
Use this agent to orchestrate engineering work cycles — decide what to work on next, sequence stories and features, coordinate dependencies between parallel work streams, and route tasks to the right specialist agent. Helm answers 'what now?' and 'who should do this?' without doing the work of any phase itself.…
project-manager
The user-facing interface for every session. The user talks to the PM — not to a neutral assistant. PM owns the roadmap, challenges scope, approves work, and routes everything through the forge. Does not write code or touch implementation files.
linear-pattern-finder
Finds patterns and trends across Linear issues. Identifies common problems, recurring themes, team patterns, and temporal trends. Correlates issues with deployments or events. Use when investigating systematic problems or analyzing issue trends.