skills.rest
ShubhamManachekar
ShubhamManachekarCOMMUNITY
Explore all skills by this author →
GitHub

middleware-handlers

Route and secure asynchronous messages with HMAC-SHA256 signing and key rotation.

Updated Mar 5, 2026
Search Tags:#security#message-queue#pubsub#fault-tolerance#eventbus#hmac-sha256
One-click install
npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill middleware-handlers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: middleware-handlers
Source: https://github.com/ShubhamManachekar/GeoSupply/tree/main/.agent/skills/middleware-handlers
Command: npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill middleware-handlers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The EventBus handles all asynchronous communication and lateral routing across the swarm. The rules here dictate how to govern this middleware logically without generating traffic mock buffers.

Core Features & Use Cases

  • HMAC-SHA256 signing and verification: Every message on the bus must be signed by the agent's key and verified by the receiver; key rotations occur every 30 days to ensure credential freshness.
  • No bypass rules: Do not allow unsigned inputs onto the bus unless strictly flagged for Tier 0 ingestion bypass processing.
  • Reliability & isolation: When multiple subagents subscribe to a topic, an exception in one handler must not crash the publish queue; test this by injecting a bad event and confirming the good handler still executes.
  • Resource controls: Cap in-memory event buffers (e.g., 5000) and spill unprocessed events to disk journaling; decorate slow consumers with timeouts.

Quick Start

Configure the EventBus to sign messages with the agent’s key and verify signatures on receipt.

Frequently Asked Questions about middleware-handlers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement HMAC-SHA256 signing and key rotation for an EventBus?▼

HMAC-SHA256 signing requires every EventBus message to be signed by the agent's key and verified by the receiver. Key rotations occur every 30 days to maintain credential freshness across multi-subagent topologies.

How does an EventBus handle fault tolerance when a subscriber throws an error?▼

Fault tolerance in an EventBus uses quiet-fail behavior, ensuring an exception in one handler does not crash the publish queue. This isolation allows remaining subscribers to execute normally during event flow.

What is the best way to manage back-pressure and memory use in a pub/sub system?▼

Back-pressure handling in a pub/sub system manages memory use by capping in-memory event buffers at 5000 events. Unprocessed events spill to disk journaling, and slow consumers receive timeout decorations.

How do I prevent unsigned messages from entering a message queue?▼

Message queue security dictates no bypass rules for unsigned inputs unless strictly flagged for Tier 0 ingestion bypass processing. This prevents unsigned data from entering the EventBus during lateral routing.

Can I use an EventBus for asynchronous communication across multiple subagents?▼

An EventBus handles asynchronous communication and lateral routing across multi-subagent topologies. It governs middleware logically without generating traffic mock buffers during event flow.

Related Skills

Explore More Software Engineering Skills→
AfricanDigitalAssetFrameworkAfricanDigitalAssetFramework

cowpay

Automate Cowpay integration for Egyptian payment processing with HMAC-SHA256 authentication.

Official
Advanced
adaptive-enforcement-labadaptive-enforcement-lab
3

reliability-patterns

Configure Argo Events retry and dead-letter patterns for durable event delivery.

Official
Intermediate
wshaddixwshaddix
71

dotnet-channels

Implement thread-safe producer-consumer communication using System.Threading.Channels in .NET.

Community
Advanced
rabiasohail098rabiasohail098

event-driven-architect

Design event-driven architectures with Kafka, Dapr pub/sub, and microservice patterns.

Community
Advanced