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 canbus-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/canbus-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/canbus-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/canbus-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/canbus-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/canbus-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.00041 | $0.00706 |
| Opus 5.5 | $0.00016 | $0.00282 |
| Sonnet 5.5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
canbus-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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANBus Integration
Overview
Use this skill for embedded CAN bus libraries and CANBus-Triple style projects. CAN failures are often physical-layer, bit-timing, termination, transceiver, or filter problems before they are application protocol problems.
When To Use
Use this skill when:
- The user mentions CAN, CANBus-Triple, MCP2515, SocketCAN, CANopen, J1939, UDS, OBD-II, ISO-TP, or automotive messages.
- Frames are missing, bus-off occurs, IDs are wrong, filters reject messages, or bit timing is unreliable.
- The task involves adapting a CAN example project or Arduino-style CAN platform to another board.
Do not use this skill when the target is only a generic UART/SPI issue with no CAN layer.
First Questions
Ask for:
- CAN controller/transceiver and board, such as internal CAN, FDCAN, MCP2515, or CANBus-Triple.
- Bus speed, oscillator frequency, sample point, and whether CAN FD is involved.
- Wiring, termination, transceiver voltage, and whether another known-good node is present.
- Frame IDs, standard/extended format, filters, masks, and expected traffic.
- Library/project source and current error counters, bus state, or capture.
Integration Checklist
-
Verify physical layer. Confirm CANH/CANL wiring, 120-ohm termination, common ground, transceiver enable/standby, and voltage compatibility.
-
Confirm bit timing. Controller clock, prescaler, segments, sample point, and bus speed must match the network.
-
Start with listen or loopback. Use internal loopback or listen-only mode before transmitting onto a live bus.
-
Configure filters deliberately. Disable filters temporarily or accept all frames to prove RX path before narrowing IDs.
-
Separate transport and protocol. First prove raw CAN frames, then add ISO-TP, UDS, OBD-II, J1939, or application decoding.
-
Protect live systems. Do not transmit on vehicle or production buses without explicit approval and a safe test plan.
Common Failures
- Missing termination or wrong transceiver standby pin.
- MCP2515 oscillator frequency differs from library assumption.
- Standard versus extended ID mismatch.
- Filters silently drop expected frames.
- Bus-off caused by transmitting at wrong bit rate.
- SPI-to-CAN driver works in loopback but fails due to transceiver wiring.
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 · 84 lines · 41 tokens per session scan A 442784b34182
canbus-integration is a skill published in the GitHub repository easyzoom/aix-skills (38 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 706 once invoked, about $0.0002 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
routeros-mac-telnet
MAC-Telnet protocol (MikroTik Layer-2 terminal/exec over UDP 20561) wire format, session handshake, and MD5 + MTWEI (EC-SRP) authentication. Use when: implementing or debugging a MAC-Telnet client/server, reaching a RouterOS device by MAC address without IP, parsing MAC-Telnet packets, understanding the WinBox-style…
routeros-syntax-inspection
Inspecting and validating RouterOS command/script syntax against a live device via /console/inspect (highlight, completion, syntax, child) and :parse IL. Use when: validating RouterOS commands before execution, explaining or linting RouterOS scripts, building syntax-aware tooling (LSP servers, validators, agent…
routeros-sniffer
RouterOS packet capture and TZSP streaming for protocol debugging. Use when: capturing packets on RouterOS, setting up /tool/sniffer, streaming live traffic via TZSP, using firewall mangle action=sniff-tzsp, debugging network protocols on MikroTik, receiving TZSP with Wireshark or tshark, saving pcap files from…
tia-doctor
Manual, read-only prerequisite probe for TIA Portal V21 and its modular Openness API, with an optional Python TIA Scripting check.
embedded-debugging
Debug embedded firmware on real hardware through the jlink-mcp server — crashes, hangs, peripheral misconfiguration, silent devices. Covers loading ELF symbols for source-level backtraces, supplying an SVD for named peripheral fields, and the halt/read/resume discipline. Use whenever debugging a microcontroller over a…
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.