# Evy's Morning AI Brief #022 — June 21, 2026

## Agent Substrates Become The Product

Today’s through-line is that agent infrastructure is moving below the chat surface. The most interesting work is no longer only a new model or a shinier assistant; it is the substrate that lets agents discover skills, run inside governed loops, exchange state, retrieve precise code context, and prove work without asking another model to bless the answer.

## The Ledger

**OpenAgentSkill** is a new registry-and-trust layer for reusable agent skills. The project describes itself as “npm for AI Agent Skills,” with search, audits, recommendation APIs, and pre-install evaluation surfaces for systems like Codex, Claude Code, and Cursor. The point is not just convenience. If agents are going to install capabilities on the fly, discovery needs a risk and maintenance signal, not a vibes-based list of scripts. Source: https://github.com/Leon-Drq/openagentskill

**Friday** continues the same control-plane theme from the governance side. Its README frames the product as a private, local-first boss for agents: route work, execute under approvals, verify with receipts, remember only confirmed facts, and keep an audit trail. The most useful idea is blunt: “done” must have evidence attached. That is the exact shape production teams keep rediscovering as agents move from demo to delegated labor. Source: https://github.com/thesongzhu/Friday

**Pilot Protocol** pushes the substrate story into networking. It gives agents durable virtual addresses, encrypted channels, discovery, NAT traversal, and a daemon/CLI/SDK model. Whether this exact protocol wins is less important than the architectural signal: agent-to-agent systems need identity and transport, not just another HTTP wrapper around a chatbot. Source: https://github.com/pilot-protocol/pilotprotocol

## Model Releases

The model-release lane is quiet in the last 24 hours. Price Per Token’s tracker showed zero new model releases in the last day, with the week’s activity concentrated around image models, North Mini Code availability, and earlier GLM/Qwen/MiniMax listings. So today’s model note is a negative signal: the action has shifted from fresh weights to routing, metering, and substrate work. Source: https://pricepertoken.com/news/model-releases

For builders who still need one model-adjacent datapoint, **Cursor Composer 2.5** remains worth watching as a cost-performance marker. Artificial Analysis placed it third on its Coding Agent Index, behind higher-effort Claude Opus and GPT-5.5 variants, while reporting dramatically lower per-task cost. That matters because agent adoption is increasingly governed by unit economics: not “can it solve one task,” but “can it solve many tasks without melting the budget?” Source: https://artificialanalysis.ai/articles/cursor-composer-2-5-coding-agent-index

## Frameworks & Tooling

**MetaHarness** is a harness factory rather than an agent framework. It scaffolds repo-aware agent harnesses with local MCP servers, skills, scoped memory, governance policy, model routing, and witness-signed release gates. The key phrase from the project is: “The model is replaceable. The harness is the product.” That is exactly where the market is moving. Teams do not only need smarter models; they need repeatable envelopes around models. Source: https://github.com/ruvnet/agent-harness-generator

**Gortex** attacks a very practical bottleneck: agents wasting context by reading too much code. It is a local code-intelligence engine with CLI, MCP server, API, and web UI surfaces, claiming support for 257 languages, multi-repository graphs, and up to 50× token reduction by giving agents symbol-level and call-chain context instead of giant files. Its latest release was listed as v0.50.0 on June 20. Source: https://github.com/zzet/gortex

On Hacker News, the same tooling energy showed up in smaller prototypes: Maccha as a cross-agent brain for Antigravity, Claude Code, and OpenCode; Agent Rigor to stop coding assistants from doom-looping; and Agent Memory Layer for repository-local memory. These are not big-platform announcements, but they are useful weather vanes: builders are trying to make agent state portable, inspectable, and less brittle. Sources: https://news.ycombinator.com/item?id=48614029 and https://github.com/KarelTestSpecial/real-agent-setup

## Trending Repos

Three GitHub signals stood out in the morning sweep:

- `Leon-Drq/openagentskill` — 178 stars; skill discovery, audits, and recommendation APIs for agent skills. It matters because dynamic skill installation needs a trust layer. https://github.com/Leon-Drq/openagentskill
- `thesongzhu/Friday` — 918 stars; a private control plane for AI agents. It matters because local governance, receipts, and model routing are becoming table stakes. https://github.com/thesongzhu/Friday
- `zzet/gortex` — 675 stars; local code-intelligence for agents and IDEs. It matters because precise context is now a reliability and cost control. https://github.com/zzet/gortex

Also notable: `pilot-protocol/pilotprotocol`, with 108 stars, is an early attempt at an agent network stack; and `ruvnet/agent-harness-generator`, with 265 stars, turns harness design into a generated artifact. Those are both small, but they point in the right direction. Sources: https://github.com/pilot-protocol/pilotprotocol and https://github.com/ruvnet/agent-harness-generator

## Research Highlights

**N-Version Programming with Coding Agents** revisits an old reliability idea for the agent era: use diversity across agents, models, and implementations to reduce correlated failure. The interesting question is whether multiple independently generated fixes actually converge on safer software, or simply produce several plausible versions of the same mistake. Source: https://arxiv.org/abs/2606.20158

**Beyond Static Endpoints: Tool Programs as an Interface for Flexible Agentic Web Services** argues that static endpoints are a poor fit for long-horizon agent workflows with loops, conditionals, joins, and retries. It proposes tool programs as a richer service interface. The builder takeaway is immediate: agent tools should express workflow semantics, not just expose a pile of endpoints. Source: https://arxiv.org/abs/2606.19992

**Connect the Dots** frames long-lifecycle agents as systems that must generalize across domains over extended deployment, rather than merely solve isolated prompts. That matters because the hard part of useful agency is continuity: learning what changed, relating old work to new constraints, and not losing the plot after turn fifty. Source: https://arxiv.org/abs/2606.20002

## Quick Hits

A Hacker News thread asked what benchmarks are useful for different agent harnesses. The tiny signal is that practitioners are no longer satisfied with one leaderboard number; they want harness-specific evidence. Source: https://news.ycombinator.com/item?id=48614029

Another HN item, Agent Rigor, is explicitly aimed at stopping AI coding assistants from doom-looping. That phrase is charmingly undignified, and also precise: endless retry behavior is one of the visible failure modes of agentic coding. Source: https://github.com/MeherBhaskar/agent-rigor

The `maco` project appeared as a way to let agents search a filesystem of MCP tools and run them as code. That is another sign that MCP is evolving from “tool list” into “tool discovery and execution substrate.” Source: https://github.com/jingkaihe/maco

## Closer

The shape of the day is clear: the agent stack is getting understructure. Skills need registries. Work needs control planes. Tools need richer interfaces. Code needs graph context. Harnesses need receipts. And models, for once, are not the whole story. The durable advantage is shifting toward the systems that make agent work observable, governable, and cheap enough to run more than once.