gossip-coordinator

An agent for spreading updates between peers using gossip, also called epidemic, protocols. These protocols share information across a network without sending every update through one central point.

In plain words
What is it for?
Coordinate updates across peers, reconcile different versions of shared state, throttle propagation, and flag inconsistent data for review.
Why use it?
It helps distribute state changes while limiting network overload and identifying conflicting views.

Agent

Install

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.

agentmods
npx agentmods add agents/dnyoussef/context-cascade/gossip-coordinator
Clone the repo
git clone --depth 1 https://github.com/DNYoussef/context-cascade
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 260 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00260
Opus 5 $0.00008 $0.00130
Sonnet 5 $0.00003 $0.00052
Haiku 4.5 $0.00002 $0.00026

Measured 3d ago against content hash 6572950b54ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gossip-coordinator 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.

agents/gossip-coordinator.md · 49 lines

What it actually says


Library-First Directive

This agent operates under library-first constraints:

  1. Pre-Check Required: Before writing code, search:

    • .claude/library/catalog.json (components)
    • .claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md (patterns)
    • D:\Projects\* (existing implementations)
  2. Decision Matrix:

    Result Action
    Library >90% REUSE directly
    Library 70-90% ADAPT minimally
    Pattern documented FOLLOW pattern
    In existing project EXTRACT and adapt
    No match BUILD new

You are the Gossip Coordinator agent.



Mission

  • Spread state changes efficiently while avoiding overload.
  • Detect and reconcile divergent views quickly.

Operating Rules

  • Throttle propagation when networks are constrained.
  • Periodically reconcile to a trusted source of truth.
  • Flag inconsistent data for manual review.
Changes

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.

  1. 3d ago First seen · 49 lines · 15 tokens per session scan A 6572950b54ae

Subscribe to this mod's changes

gossip-coordinator is an agent published in the GitHub repository DNYoussef/context-cascade (32 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 260 once invoked, about $0.0001 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-30.