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.
npx skills add easyzoom/aix-skills --skill lwip-integrationgit clone --depth 1 https://github.com/easyzoom/aix-skillsWrote 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/easyzoom/aix-skills/lwip-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/lwip-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/lwip-integration/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/easyzoom/aix-skills/lwip-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/lwip-integration.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.00042 | $0.00859 |
| Opus 5 | $0.00021 | $0.00430 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
lwip-integration 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lwIP Integration
Overview
Use this skill to integrate lwIP by separating hardware Ethernet/Wi-Fi drivers, netif glue, memory pools, threading model, and protocol configuration. A successful port proves link, IP configuration, packet RX/TX, and resource stability under load.
When To Use
Use this skill when:
- The user wants to add or debug lwIP on bare metal, FreeRTOS, RT-Thread, Zephyr, vendor SDKs, or custom network drivers.
- The issue involves
lwipopts.h,sys_arch,netif, DHCP, TCP/UDP, pbufs, memory pools, packet loss, or hard faults in networking. - The target uses Ethernet, Wi-Fi, PPP, SLIP, or a vendor network interface.
Do not use this skill when the physical link or board interface is not proven. Use hardware-interface-debug first for PHY, RMII/MII, clocks, or wiring issues. For FreeRTOS-native TCP/IP, use freertos-plus-tcp-integration. For MQTT over lwIP, use mqtt-embedded-integration after basic connectivity works.
First Questions
Ask for:
- MCU/SoC, network interface, PHY/module, RTOS, and lwIP version.
- Driver source: vendor SDK, custom MAC driver, Wi-Fi module, or simulator.
- Threading model: NO_SYS raw API, tcpip_thread, socket/netconn API, or RTOS integration.
lwipopts.h, memory sizes, pbuf pool settings, and enabled protocols.- Current symptom: no link, no IP, DHCP timeout, ping fails, TCP stalls, memory exhaustion, or crash.
- Packet/log evidence: link status, IP address, ARP, ping, Wireshark, counters, or asserts.
Integration Checklist
-
Confirm link before IP. Verify PHY/module link, MAC address, link callbacks, and carrier status before debugging DHCP or TCP.
-
Confirm
netifglue.netif_add, input path, output path, MTU, flags, hostname, and link/status callbacks must match the driver. -
Match threading model. Do not call raw API from arbitrary threads. Use tcpip callbacks or socket/netconn APIs according to configuration.
-
Size memory deliberately. Check
MEM_SIZE,MEMP_NUM_*,PBUF_POOL_SIZE, TCP windows, mailbox sizes, and stack sizes.
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.
- 10d ago First seen · 85 lines · 42 tokens per session scan A 56ed5cca9f93
lwip-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 859 once invoked, about $0.0002 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.
Other skills, from other repositories
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
n8n-workflow
Design, build, or troubleshoot n8n automation workflows. Always trigger immediately when Mick mentions n8n, workflow nodes, automating a pipeline, or connecting services via n8n. Covers node selection, webhook patterns, Claude API integration, credential setup, Cloudflare Tunnel exposure, and Proxmox LXC deployment.…
amazon-alexa
Integracao completa com Amazon Alexa para criar skills de voz inteligentes, transformar Alexa em assistente com Claude como cerebro (projeto Auri) e integrar com AWS ecosystem (Lambda, DynamoDB, Polly, Transcribe, Lex, Smart Home).
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.