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.
git clone --depth 1 https://github.com/amyodov/yet-another-agentic-chatWrote 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/plugins/amyodov/yet-another-agentic-chat/plugin)<a href="https://agentmods.dev/plugins/amyodov/yet-another-agentic-chat/plugin"><img src="https://agentmods.dev/badge/plugins/amyodov/yet-another-agentic-chat/plugin/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.
<a href="https://agentmods.dev/plugins/amyodov/yet-another-agentic-chat/plugin"><img src="https://agentmods.dev/badge/plugins/amyodov/yet-another-agentic-chat/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
yaac 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.
What it actually says
{
"name": "yaac",
"displayName": "YAAC",
"version": "0.6.0",
"description": "Messaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure. (YAAC: Yet Another Agentic Chat.)",
"author": {
"name": "Alex Myodov",
"email": "[email protected]"
},
"homepage": "https://github.com/amyodov/yet-another-agentic-chat",
"repository": "https://github.com/amyodov/yet-another-agentic-chat",
"license": "MIT",
"keywords": [
"mcp",
"chat",
"messaging",
"agents",
"zeromq"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 102 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed 9935f7b18666
- 1mo ago Changed 4d317e6737fd
- 1mo ago First seen · 21 lines scan A 219dacebeef8
yaac is a plugin published in the GitHub repository amyodov/yet-another-agentic-chat (3 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
agent-relay
Lets your Gemini CLI sub-agents communicate with each other in real time.
rn-dev-agent
AI agent that fully tests React Native features on simulator/emulator — navigates the app, verifies UI, walks user flows, and confirms internal state.
agent-comms marketplace
Plugin marketplace listing 1 plugin: agent-comms.
agent-comms
Cross-harness LLM agent communication mesh — rooms, DMs, and presence.
software-factory
Lanes, tickets, and a human merge. Same skills as Cursor, Grok, and Codex.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.