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 avem-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/avem-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/avem-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/avem-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/avem-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/avem-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.00033 | $0.00593 |
| Opus 5.5 | $0.00013 | $0.00237 |
| Sonnet 5.5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
avem-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 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.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Avem Integration
Overview
Use this skill when the user explicitly works with an embedded framework or library named Avem. Because public references can be sparse or project-specific, first confirm the exact repository and then treat Avem as an architecture-level dependency with explicit platform hooks and module boundaries.
When To Use
Use this skill when:
- The user mentions Avem in an MCU, embedded C, firmware framework, middleware, or application architecture context.
- The task involves adapting Avem modules, drivers, event loops, services, or platform hooks.
- The user wants to evaluate whether Avem fits a project.
Do not use this skill when "Avem" refers to an unrelated product, service, or non-embedded codebase.
First Questions
Ask for:
- Exact Avem repository/source and version.
- Target MCU/SoC, RTOS/bare-metal runtime, compiler, and build system.
- Which Avem modules are needed.
- Required platform hooks: timebase, allocator, logging, storage, drivers, event loop, or RTOS primitives.
- Current goal: evaluation, first port, compile fix, runtime bug, or migration.
Integration Checklist
-
Confirm identity and scope. Read the project's own docs/source layout before assuming Avem behavior.
-
Identify platform hooks. Time, memory, logging, synchronization, drivers, and initialization order must be mapped to the target.
-
Start with one module. Bring up the smallest useful Avem module before importing the full framework.
-
Keep boundaries explicit. Application code should not depend on hidden globals or framework internals unnecessarily.
-
Verify resource impact. Measure flash, RAM, stack, heap, and scheduler impact if Avem becomes a core dependency.
Common Failures
- Assuming Avem's API from another framework with a similar pattern.
- Importing the entire framework before one module works.
- Platform hooks silently use unavailable malloc, file I/O, or RTOS functions.
- Initialization order depends on undocumented global state.
- Framework callbacks block timing-sensitive driver paths.
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 · 80 lines · 33 tokens per session scan A d10804819d29
avem-integration is a skill published in the GitHub repository easyzoom/aix-skills (38 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 593 once invoked, about $0.0001 per session on Opus 5.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.
lab-hardware-cad
Designs custom laboratory hardware as parametric build123d models and exports fabrication artifacts as STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a…
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
opentrons-integration
Authors, reviews, migrates, simulates, and troubleshoots official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one…
pylabrobot
Develops and reviews PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Supports PyLabRobot protocols and API questions; keep physical execution behind an explicit operator safety gate.
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).