Mesh LLM is a distributed AI system that combines GPUs and memory from multiple machines and exposes them through one OpenAI-compatible inference server, which is a service that runs models and answers API requests. It is for people who want to share compute privately or publicly to run models for agents and chat, including models too large for one machine. The catalogue add-ons support workflows for operating and using the mesh.
Borrowing it
Nothing to install: this file belongs to Mesh-LLM/mesh-llm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Mesh-LLM/mesh-llm/main/.agents/skills/llama-stage-patch-changes/SKILL.mdgit clone --depth 1 https://github.com/Mesh-LLM/mesh-llmWrote 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/mesh-llm/mesh-llm/llama-stage-patch-changes)<a href="https://agentmods.dev/skills/mesh-llm/mesh-llm/llama-stage-patch-changes"><img src="https://agentmods.dev/badge/skills/mesh-llm/mesh-llm/llama-stage-patch-changes.svg" alt="Measured on agentmods" 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.00051 | $0.02138 |
| Opus 5 | $0.00026 | $0.01069 |
| Sonnet 5 | $0.00010 | $0.00428 |
| Haiku 4.5 | $0.00005 | $0.00214 |
Grade C, and why
llama-stage-patch-changes scanned grade C 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
trap 'rm -rf -- "$tmp_root"' EXIT How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
llama-stage-patch-changes
Use this skill when changing the Skippy staged-runtime ABI carried in
third_party/llama.cpp/patches.
Boundaries
- Keep durable llama.cpp-side changes in
third_party/llama.cpp/patches/*.patch. - Keep the upstream pin in
third_party/llama.cpp/upstream.txt. - Do not edit
.deps/llama.cppas the final artifact; regenerate the patch queue from commits. - Keep mesh orchestration, protocol compatibility, lifecycle, model management, and API status behavior in Rust.
- Keep one functional boundary per patch. Patch numbers must be unique and contiguous.
- Keep public ABI declarations separate from independently reviewable model lifecycle, loading, and package implementation changes.
- The Skippy native ABI is an internal lockstep boundary, not a stable cross-version compatibility contract. It may change whenever the feature requires it; update the Rust FFI mirror and all callers in the same change.
- Do not preserve old native ABI signatures for compatibility. Bump the ABI version when the boundary changes so mismatches are diagnosable, and make sure the shipped Rust side and native runtime are built from the same queue.
- Do not add a terminal source-reorganization patch. A deliberate layout or ownership change must be represented in the recreated patches that own the affected capabilities.
Native Source Layout
include/skippy.his an umbrella only. Put public C ABI declarations in standaloneinclude/skippy/<capability>.hheaders.- Put implementations in
src/skippy/<capability>.cppand private C++ declarations in narrowly namedsrc/skippy/*.hheaders. - Use
snake_casecapability names. Keep exported symbols prefixed withskippy_and avoid generichelpers,utils, or expandedcommonmodules. src/skippy.cppis retired. Extend the owning capability module and keep new implementation files below 1,000 lines.- Make every public header independently compilable as both C11 and C++17. Update explicit CMake source lists and installation rules with new modules.
- Do not preserve retired source include paths unless the task explicitly asks for compatibility. Continue to version and mirror any binary ABI change.
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.
- 7d ago First seen · 204 lines · 51 tokens per session scan C 2fb689d98880
llama-stage-patch-changes is a skill published in the GitHub repository Mesh-LLM/mesh-llm (3,358 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 2,138 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
developing-genkit-tooling
Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
zcfg
Integrate zcfg (Zero Dependency Configuration Utility) into Java applications. Use when adding configuration loading, reading properties files, setting up application configuration, or integrating zcfg into a Java project. Triggers on "zcfg", "add configuration", "load properties", "application configuration with…
data-structures
Implements custom JavaScript data structures: queues, deques, stacks, linked lists, cons lists, circular buffers, unrolled lists, tries, heaps, graphs, LRU caches, CRDTs, pools, structs. Use when building or choosing non-native collections, optimizing enqueue/dequeue, designing persistent lists, or when the user asks…
microprofile-server
Architecture and coding rules for long-running Java MicroProfile / Jakarta EE server applications — BCE layering, business components (BC), JAX-RS resources, CDI, JSON-P, testing (unit/integration/system), and Maven project structure. Use when creating, generating, scaffolding, writing, or reviewing code, resources…
bce
Generic, composable architecture rules for the Boundary-Control-Entity (BCE/ECB) pattern — business components, layer responsibilities, package structure, and cross-component relationships. Technology-neutral; meant to be composed with language- or framework-specific skills (e.g. microprofile-server, web-components…