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 agentmods add skills/simra-tech/openada/close-layout-incrementallynpx skills add simra-tech/OpenADA --skill close-layout-incrementallygit clone --depth 1 https://github.com/simra-tech/OpenADAWhat 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 | $0.00098 | $0.01750 |
| Opus 5 | $0.00049 | $0.00875 |
| Sonnet 5 | $0.00020 | $0.00350 |
| Haiku 4.5 | $0.00010 | $0.00175 |
Grade A, and why
close-layout-incrementally 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 2d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Layout Incrementally
Treat visual inspection as a required diagnostic loop and tool-native evidence
as the engineering gate. Use $openada:openada for capability discovery, DRC,
LVS, simulation, and normalized result interpretation. Keep the selected PDK,
rule deck, extraction setup, schematic, models, and native layout authoritative.
Freeze one closure context
Record before editing:
- writable layout and immutable baseline hashes;
- exact cell and hierarchy boundary under review;
- authoritative PDK revision, layer map, DRC deck, LVS setup, extraction setup, models, schematic/netlist, and simulator startup chain;
- device intent, net intent, matching or symmetry constraints, current paths, sensitive nodes, and supplied DRC/LVS/parasitic/performance limits;
- known-good DRC, LVS, PEX, and simulation evidence for the baseline.
Do not mix collateral revisions to obtain a pass. If the authoritative process context is ambiguous, stop before changing geometry and request that choice.
Choose the smallest meaningful increment
Change one independently reviewable unit:
- one device or matched device pair;
- one contact or via array;
- one local route or critical-net segment;
- one guard-ring, well, tap, shield, or power connection;
- one block-boundary pin or one hard-macro integration edge.
Do not place or connect the whole block at once. Preserve the prior passing checkpoint. State the expected connectivity and parasitic effect before the edit, including the planned route and return path.
For matched or high-frequency structures, begin with the minimum meaningful pair. Close that pair before adding bias, load, cascode, common-mode, or routing structures. Repeat the same rule when joining completed blocks: connect one interface or critical net, then reclose the hierarchy.
Render before and after every edit
Produce all views needed to understand the increment:
- full-cell context with hierarchy visible;
- marker-centered zoom with coordinates and scale;
- isolated device, cut, and adjacent conductor layers;
- connectivity context one level above and below the edited cell;
- before/after views at the same crop, layer visibility, and resolution.
What ships with it
2 files 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.
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.
- 2d ago First seen · 173 lines · 98 tokens per session scan A 37c62cbc425d
close-layout-incrementally is a skill published in the GitHub repository simra-tech/OpenADA (24 stars, last pushed 20d ago), licensed MIT. It adds 98 tokens to every session and 1,750 once invoked, about $0.0005 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
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.
cli-anything-3mf
3MF mesh geometry editor — detect and resize cylindrical holes, repair meshes, compare 3D printing files. Works with BambuStudio and PrusaSlicer 3MF files.
platform-port
Guide porting FastLED to new MCU platforms, including int.h types, clockless drivers, SPI implementations, and platform detection. Use when adding support for a new microcontroller family or board.
doca-compress
Use this skill for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or decompress-lz4-block tasks on a docacompress context (the hardware supports DEFLATE both directions plus LZ4 decompress; LZ4 encode is NOT…
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…
anta-validation
Validate Arista EOS network state with structured pass/fail verdicts using ANTA. Use for "is this switch healthy", "did my change break anything", "verify BGP/interfaces/hardware are correct", "run a health check on this device". Read-only. A test for a feature the device does not run reports notapplicable — never a…