Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/alonf/MCPPythonDemonpx agentmods add skills/alonf/mcppythondemo/distributed-meshWrote 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/skills/alonf/mcppythondemo/distributed-mesh)<a href="https://agentmods.dev/skills/alonf/mcppythondemo/distributed-mesh"><img src="https://agentmods.dev/badge/skills/alonf/mcppythondemo/distributed-mesh/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/skills/alonf/mcppythondemo/distributed-mesh"><img src="https://agentmods.dev/badge/skills/alonf/mcppythondemo/distributed-mesh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.03069 |
| Opus 5.5 | $0.00006 | $0.01228 |
| Sonnet 5.5 | $0.00003 | $0.00614 |
| Haiku 4.5 | $0.00002 | $0.00307 |
Grade A, and why
distributed-mesh scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Zone 3 — Remote-Opaque:** Different org, no shared auth. Transport: `curl` to fetch published contracts (SUMMARY.md). One-way visibility — you see only what they publish. This is a copy
100% identical to distributed-mesh — 574 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCOPE
✅ THIS SKILL PRODUCES (exactly these, nothing more):
mesh.json— Generated from user answers about zones and squads (which squads participate, what zone each is in, paths/URLs for each), usingmesh.json.examplein this skill's directory as the schema templatesync-mesh.shandsync-mesh.ps1— Copied from this skill's directory into the project root (these are bundled resources, NOT generated code)- Zone 2 state repo initialization (if applicable) — If the user specified a Zone 2 shared state repo, run
sync-mesh.sh --initto scaffold the state repo structure - A decision entry in
.squad/decisions/inbox/documenting the mesh configuration for team awareness
❌ THIS SKILL DOES NOT PRODUCE:
- No application code — No validators, libraries, or modules of any kind
- No test files — No test suites, test cases, or test scaffolding
- No GENERATING sync scripts — They are bundled with this skill as pre-built resources. COPY them, don't generate them.
- No daemons or services — No background processes, servers, or persistent runtimes
- No modifications to existing squad files beyond the decision entry (no changes to team.md, routing.md, agent charters, etc.)
Your role: Configure the mesh topology and install the bundled sync scripts. Nothing more.
Context
When squads are on different machines (developer laptops, CI runners, cloud VMs, partner orgs), the local file-reading convention still works — but remote files need to arrive on your disk first. This skill teaches the pattern for distributed squad communication.
When this applies:
- Squads span multiple machines, VMs, or CI runners
- Squads span organizations or companies
- An agent needs context from a squad whose files aren't on the local filesystem
When this does NOT apply:
- All squads are on the same machine (just read the files directly)
Patterns
The Core Principle
"The filesystem is the mesh, and git is how the mesh crosses machine boundaries."
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 288 lines · 16 tokens per session scan A a9e91ed408df
distributed-mesh is a skill published in the GitHub repository alonf/MCPPythonDemo (0 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 3,069 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to distributed-mesh, differing in 574 lines, and is treated as a copy.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…