What is og-device-ops?

A set of instructions for operating OpenGate IoT devices through the og command-line tool. OpenGate is a platform for managing connected devices, and the instructions cover device actions, alarms, data injection, rules, connectors, and operation jobs.

Launching and cancelling jobs, managing alarms, defining operation types, deploying automation rules and connector code, and performing other device operations after logging in.

It helps prevent accidental device changes by distinguishing read actions from actions that affect devices and requiring confirmation before irreversible commands.

How carlosprados/og-cli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to carlosprados/og-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/carlosprados/og-cli/main/.claude/skills/og-device-ops/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/carlosprados/og-cli

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/carlosprados/og-cli/og-device-ops/github.svg)](https://agentmods.dev/skills/carlosprados/og-cli/og-device-ops)

Your own site

<a href="https://agentmods.dev/skills/carlosprados/og-cli/og-device-ops"><img src="https://agentmods.dev/badge/skills/carlosprados/og-cli/og-device-ops/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/carlosprados/og-cli/og-device-ops"><img src="https://agentmods.dev/badge/skills/carlosprados/og-cli/og-device-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 164 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,203 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00164	$0.06203
Opus 5.5	$0.00066	$0.02481
Sonnet 5.5	$0.00033	$0.01241
Haiku 4.5	$0.00016	$0.00620

Measured 2mo ago against content hash 700ae4dea3c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

og-device-ops 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 2mo 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.

.claude/skills/og-device-ops/SKILL.md · 446 lines

How it starts

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

OpenGate device operations skill

Acting ON devices (vs querying them — that's the og-cli skill): operations, alarms, and data injection. All commands need a logged-in profile (og login).

Destructive operations — confirm BEFORE running (HITL)

delete and cancel verbs are irreversible. og guards them: on an interactive terminal it prompts [y/N]; non-interactively it REFUSES unless --yes is passed (Error: refusing to delete ... re-run with --yes (no interactive terminal)). You drive og non-interactively, so that terminal prompt never reaches the user — the safeguard is YOURS to honor:

STOP before any destructive command. State exactly what it affects — verb, id, org/channel, and what is lost (e.g. "delete device sense-001 in org acme — removes the entity and its collected data").
Ask the user and wait for an explicit yes.
Only then run it with --yes (required non-interactively).

Never add --yes reflexively to silence the "refusing…" error — that error means ask the user first, not append a flag.

Destructive verbs: dev delete, jobs cancel, tasks cancel, dm delete, connectors delete, rules delete, optypes delete, provision delete, timeseries delete, datasets delete, workspace delete, dashboard delete. Treat deploy --update (overwrites) and bulk provision runs as high-impact too — confirm scope first.

Jobs — one-shot operations on devices

A job = an operation (REBOOT_EQUIPMENT, EQUIPMENT_DIAGNOSTIC, ...) targeted at N devices, with schedule/timeout/retry semantics. Lifecycle:

og jobs create -f job.json          # launch, ONE batch (max 100 entities)
og jobs launch -f job.json --entities-file ids.txt   # any fleet size, batched
og jobs get <job-id>                # report: report.summary.status
og jobs operations <job-id> --all   # per-device results — check THIS for partial failures
og jobs history --job <job-id> --all    # same results, filterable, across jobs
og jobs cancel <job-id>             # stop a running job
og jobs search -w "jobStatus eq IN_PROGRESS"
og jobs search -w "operationName eq REBOOT_EQUIPMENT"

Read the full file on GitHub · 446 lines

Files

What ships with it

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

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.

2mo ago First seen · 446 lines · 164 tokens per session scan A 700ae4dea3c6

Subscribe to this mod's changes

og-device-ops is a skill published in the GitHub repository carlosprados/og-cli (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 164 tokens to every session and 6,203 once invoked, about $0.0007 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-31.

Hardware and IoT

og-device-ops next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
og-device-opscarlosprados/og-cli	Skill	2	1mo ago	Apache-2.0	A	164	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
jetson-diagnosticNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code, Codex
holoscan-install-wheelNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	34	Claude Code, Codex
offensive-z-waveSnailSploit/Claude-Red	Skill	10k	25d ago	MIT	A	113	Claude Code, Codex
doca-socket-relayNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	236	Claude Code, Codex
hsb-flashNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	B	94	Claude Code

og-cli: Skill for Claude Code