fan-out
Skill0 starsChanged 7 months agoMITView on GitHub
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Suge8/friedbuntheir own version, first seen Nov 8, 2026
- keli-wen/rondotheir own version, first seen Oct 25, 2026
- stjarnstrom/spec-systemtheir own version, first seen Oct 15, 2026
- keli-wen/dev-skillstheir own version, first seen Oct 13, 2026
- me2resh/apexyardtheir own version, first seen Oct 8, 2026
- alexanderpino/skillstheir own version, first seen Sep 15, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- me2resh/apexyard★ 542same name
- keli-wen/dev-skills★ 12same name
- keli-wen/rondo★ 12same name
- Suge8/friedbun★ 12same name
- alexanderpino/skills★ 1same name
- darrenCWJ/agent-skills-scaffold★ 0same name
- haliphax-ai/skills★ 0same name
- stjarnstrom/spec-system★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-trailSkill
- authSkill
- observabilitySkill
- rate-limitingSkill
- response-cachingSkill
- schema-validationSkill
- tool-allowlistSkill
The file
We found no rules to list in this file: it reads as prose or reference rather than instructions.
Files
Fan-out Routing
Capability
Broadcast MCP requests to multiple upstream servers with configurable aggregation strategies, circuit breaker, and retry logic.
Package
@reaatech/mcp-gateway-fanout — packages/fanout/src/
Components
| Component | Purpose |
fanout-router.ts | Multi-upstream orchestration: executeFanout, setUpstreamCaller |
response-aggregator.ts | Aggregation by strategy (first-success, all-wait, majority-vote) |
upstream-selector.ts | Weight-based upstream selection (round-robin, weighted, health-based) |
failover-handler.ts | Circuit breaker, retry with backoff, health tracking |
upstream-client.ts | JSON-RPC request creation and upstream HTTP calls |
retry-logic.ts | Exponential backoff with jitter and idempotency keys |
health-checker.ts | Periodic upstream health probes with configurable thresholds |
connection-pool.ts | HTTP Keep-Alive connection pooling for upstream requests |
Aggregation Strategies
| Strategy | Behavior |
first-success | Return first valid response, cancel others |
all-wait | Wait for all responses, merge results |
majority-vote | Return consensus from multiple upstreams |
Error Handling
- Partial failures handled gracefully (return available results)
- Timeout on slow upstreams (configurable per upstream)
- Circuit breaker prevents cascading failures
- Fan-out metadata included in response
Security Considerations
- SSRF protection on all upstream URLs (via core package)
- Each upstream call uses same auth context as original request
- Circuit breaker state configurable per upstream
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.