Tools, platforms and infrastructure of the agent ecosystem.
21 fiches · 43 entities · Updated
The agent ecosystem rests on concrete tools, platforms, and infrastructure, and cataloging them is the work here. Coding assistants and autonomous agents; the runtimes and orchestration layers beneath them; the connective tissue — protocols, model-context interfaces, IDEs, CI integrations — that lets them touch real systems: each gets examined for what it does and how its harness is built. The consolidation of assistants, runtimes, and context protocols into fewer stacks is a running thread, as is the question of which layer captures the most value. Where a tool sits in a workflow matters as much as raw capability. This is the technical substrate of AI-assisted development, described as it is actually assembled.
Key figures
$0.10 / 1M tokens input, $0.40 / 1M tokens output
Gemini 2.5 Flash-Lite · stated in source
1 million token context window
Gemini 2.5 Flash-Lite · stated in source
$3 million raised (May 2025)
Plakar · stated in source
réduction de 45% de la latence des diagnostics onboard
Product announcement from Stack Overflow (official blog) launching **Stack Overflow for Agents**, an *API-first* knowledge-exchange platform designed for the agentic era. Founding thesis: coding agents work **in isolation**, without access to a shared, verified knowledge base. Hence the **"Ephemeral Intelligence Gap"** — agents worldwide independently solve the same problems, wasting tokens and compute, then lose the solution at the end of the session; the same architecture patterns are rediscovered in a loop. Guiding principle: *"generating plausible answers has become cheap, but verifying which ones hold up in production hasn't."* Four-step workflow: **search first** (consume validated knowledge) → **contribute if a gap exists** (the agent drafts, the human approves before publication) → **verify** (results, modifications, context conditions) → **compound the signals** (votes, answers, verifications produce a consensus). Three machine-readable formats: **Questions**, **TIL** (debug traces), **Blueprint** (reusable patterns, highest quality bar). Trust rests on **community moderation** and **multi-agent verification loops**; humans claim ownership of their agent via Stack Overflow SSO (a "community anchor" tying the agent to a human reputation). Differentiated benefits: developers (fewer retry loops), AI labs (high-signal data for fine-tuning/eval), enterprises (**Stack Internal**, a proprietary knowledge layer with no data exfiltration).
#Stack Overflow for Agents#coding agents#knowledge base
Blog post by **Pasquale Pillitteri** (software engineer, Palermo) published on **May 29, 2026** (FR version), 18-minute read, *Claude Code & Anthropic* section. **Pivot thesis**: *"Claude Opus 4.8 is the most powerful SEO model of 2026, but almost everyone uses it wrong"* — not a model problem but a **system** problem. The golden rule: ***"strategy is a whiteboard, production is an assembly line"*** — **SEO must be split into two distinct phases**, and mixing them is *"the fastest way to waste a model that costs five dollars per million input tokens and twenty-five per million output tokens"*. **Model context**: Opus 4.8 released on **May 28, 2026** (41 days after Opus 4.7), **1M-token** context, **GraphWalks Long-Context F1 at 1M: 40.3% → 68.1%**, **SWE-bench Verified 88.6%**, **USAMO 2026 96.7%** (+27.4 pts), **HLE with tool 57.9%**, unchanged pricing **$5/$25** per M tokens, **Fast Mode 2.5× at $10/$50**, four **effort levels** (Low, High, Extra, Max). **The central anti-pattern** = *"the giant conversation"* / **context drift**: mixing strategy, keyword research, competitive analysis and writing in a single chat produces a *"mush of contradictory intentions"* → the model drifts toward **generic best practices** ("holistic optimization", "strategic approach") instead of data-anchored content. **Phase 1 — Strategy (whiteboard, visual UI, one-off)**: dashboard / Google Sheet / Claude.ai canvas to decide while looking at the data together. **3 plays**: (a) **classified keyword research** (volume / difficulty 0-100 / intent / business potential table / priority = volume÷difficulty×business weight); (b) **visual competitive analysis** (topical coverage matrix, gaps); (c) **phased roadmap** (quick wins M1-2 / mid-term M3-6 / pillar pages M7-12). **Extra/Max** mode is justified here (*"one right strategic decision is worth a thousand well-written pages targeting the wrong keywords"*). 3 closed artifacts saved to Notion/Drive. **Phase 2 — Production (assembly line, Opus 4.8 + MCP)**: the model shifts from strategist to **execution machine**; every decision **anchored to live data** via **Model Context Protocol**. **Stack MCP minimum**: **GSC MCP** (AminForou/mcp-gsc, 500+ stars), **official Ahrefs MCP** (98 stars), **GA4 MCP**; repo `modelcontextprotocol/servers` = **86,440 stars**, **10,000+ active servers**, 97M SDK downloads/month. Setup ~35 min, monthly refresh ~20 min. **Weekly loop**: a single prompt pulls live data, builds the brief (top 10 SERP + GSC + Ahrefs), derives H2/H3, writes, checks density, suggests titles → **+45% productivity**, draft in **6-12 min** (explicit reference to **Ryan Law / Ahrefs content engineering**, 23 skills). Mention of Anthropic's **Dynamic Workflows** (up to 1,000 subagents). **4 common mistakes**: (1) not checking the numbers (mandatory spot-check, *trust & verify*); (2) fully replacing Semrush/Ahrefs (MCP is a **layer on top**, not a substitute); (3) ignoring the **paid-organic content gap** (education client case: **2,742 wasted terms / 351 opportunities** identified in 90 seconds); (4) using Opus 4.8 where **Haiku 4.5** is enough (meta descriptions, alt text). **Cost**: $1-3 per 2,500-word article. **Sonnet 4.6** suffices for recurring production, Opus 4.8 reserved for strategy. SEO-optimized and self-referential article (the author writes SEO content itself designed to rank for "Opus 4.8 SEO"). Direct convergence with **Ryan Law/Ahrefs** (cited), **systems around the model** (Dropbox/Okumura), **skills-over-prompts** (Lattice), Haiku/Sonnet/Opus model routing (Gupta token-to-outcome).
#Claude Opus 4.8#AI SEO#two-phase workflow
**Pasquale Pillitteri** — Ingénieur informatique / développeur logiciel basé à **Palerme** (Italie) · certifié Innovation Manager UNI 11814:2021. Auteur d'un blog tech actif (rubrique *Claude Code & Anthropic*) · avec une newsletter hebdomadaire (~3,4k lecteurs). Article publié en version **FR** le **29 mai 2026** (lendemain de la sortie d'Opus 4.8).