bus-drivers-i2c-spi

bus-drivers-i2c-spi is a skill for Codex from OutlineDriven/outline-driven-development. It costs 52 tokens per session (1,641 once invoked), scanned A, original, Apache-2.0.

Guidance for Linux drivers that communicate with chips over I2C or SPI, two common board-level communication buses. It covers transfers, register access, device-tree entries, and direct memory access, or DMA.

In plain words
What is it for?
Use it to draft an I2C or SPI client-driver skeleton, configure register access, create a device-tree child entry, make SPI buffers safe for DMA, or investigate probe and transfer failures.
Why use it?
It reduces errors when connecting a Linux driver to a peripheral chip, such as handling addresses, chip selects, register maps, or failed transfers. It also helps investigate bus errors such as a device not acknowledging a request.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to draft an I2C or SPI client-driver skeleton, configure register access, create a device-tree child entry, make SPI buffers safe for DMA, or investigate probe and transfer failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi
Install

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.

Any agent
npx skills add OutlineDriven/outline-driven-development --skill bus-drivers-i2c-spi
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/outline-driven-development

Made for: Codex.

Wrote 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.

agentmods badge for bus-drivers-i2c-spi

README.md
[![agentmods](https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi/github.svg)](https://agentmods.dev/skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi/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.

agentmods 80×15 button for bus-drivers-i2c-spi

Your own site · 80×15
<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/bus-drivers-i2c-spi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,641 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01641
Opus 5 $0.00026 $0.00821
Sonnet 5 $0.00010 $0.00328
Haiku 4.5 $0.00005 $0.00164

Measured 3d ago against content hash 4245ad9f2abe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

bus-drivers-i2c-spi 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 3d 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.

.devin/skills/bus-drivers-i2c-spi/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bus drivers (I2C and SPI)

Contract

Field Bound contract
Trigger Writing a Linux I2C or SPI client driver: bus registration, i2c_transfer or spi_sync, regmap over the bus, DMA-safe SPI buffers, device tree binding on bus children, or NACK and -EREMOTEIO debugging.
Authority Read-only. Writes nothing. Chat output only. No remote mutation.
Side effect Returns driver skeletons and debug commands. No source files are modified.
Done The client driver skeleton, the transfer or regmap access pattern, the DT child node, and a debug path for the reported symptom are delivered.

Inputs

  1. Device and bus (required): the chip address on I2C or chip-select on SPI, the adapter or controller, and the datasheet register map.
  2. Transfer shape (optional): register width and value width, which set regmap_config.
  3. Failure report (optional): the symptom, such as -EREMOTEIO, a stuck bus, or a probe that never runs.

Procedure

  1. Write the I2C client driver skeleton. The bus core owns the adapter; the driver owns registers only.

    #include <linux/i2c.h>
    #include <linux/mod_devicetable.h>
    
    static void my_remove(struct i2c_client *client) {}
    
    static struct i2c_driver my_driver = {
        .probe  = my_probe,
        .remove = my_remove,
        .driver = {
            .name = "mysensor",
            .of_match_table = my_of_id,
        },
        .id_table = my_id,
    };
    module_i2c_driver(my_driver);
    

    remove returns void; the int-returning form was removed from the bus driver structs in kernel 6.11, and the kernel floor here (LTS 6.18, mainline 7.2) is past it. Done when: the driver struct carries probe, remove, both match tables, and the module registration macro.

  2. Bind from the device tree child node. The reg property is the bus address.

    &i2c1 {
        sensor@48 {
            compatible = "vendor,sensor";
            reg = <0x48>;
        };
    };
    
    static const struct of_device_id my_of_id[] = {
        { .compatible = "vendor,sensor" },
        { }
    };
    MODULE_DEVICE_TABLE(of, my_of_id);
    

Read the full file on GitHub · 143 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 3d ago First seen · 143 lines · 52 tokens per session scan A 4245ad9f2abe

Subscribe to this mod's changes

bus-drivers-i2c-spi is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,641 once invoked, about $0.0003 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-09-06.

Related

Other skills, from other repositories

automatic-cybernetic-flow-design

Use when the user wants a cybernetic flow design document for an interactive system. Specifies sensors, actuators, feedback paths, delays, and oscillation risk, and writes the design to a named local file. Not for implementing or deploying the system.

OutlineDriven/odin-claude-plugin · 58 tokens

holoscan-install-wheel

Install Holoscan SDK Python wheel via pip into a venv. Use for Python installs; not for native C++/apt or Conda installs.

NVIDIA/skills · 37 tokens

unifi-protect

How to manage UniFi Protect cameras and NVR — view cameras, smart detections, Find Anything detection search, recordings, snapshots, lights, sensors, Known Faces, license plates, and the Alarm Manager. Use this skill when the user mentions UniFi cameras, security cameras, NVR, recordings, motion detection, person…

sirkirby/unifi-mcp · 112 tokens

mi300-hip-vs-nvidia

MI300 HIP programming differences vs NVIDIA—wavefront vs warp, memory hierarchy, MFMA usage, occupancy, and profiling pitfalls.

AMD-AGI/Apex · 35 tokens

gpu-memory-model

GPU memory model skill for SIMT execution and memory hierarchy. Use when analyzing warp divergence, memory coalescing, shared memory bank conflicts, cache behavior, atomics, or occupancy tradeoffs. Activates on queries about SIMT, warp coalescing, bank conflicts, wavefront, GPU occupancy, or memory-bound kernels.

mohitmishra786/low-level-dev-skills · 70 tokens

ios-build-cleanup

Use when the user wants a clean Xcode rebuild by deleting DerivedData and build artifacts. Do not use for diagnosing a specific build error: use ios-build-fix.

OutlineDriven/odin-claude-plugin · 39 tokens