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/jl-codes/platformio-mcp/sbc-deploynpx skills add jl-codes/platformio-mcp --skill sbc-deploygit clone --depth 1 https://github.com/jl-codes/platformio-mcpWrote 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/jl-codes/platformio-mcp/sbc-deploy)<a href="https://agentmods.dev/skills/jl-codes/platformio-mcp/sbc-deploy"><img src="https://agentmods.dev/badge/skills/jl-codes/platformio-mcp/sbc-deploy.svg" alt="Measured on agentmods" 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.00053 | $0.00286 |
| Opus 5 | $0.00026 | $0.00143 |
| Sonnet 5 | $0.00011 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
sbc-deploy 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 6d 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.
What it actually says
SBC Deploy
Purpose
Use this skill when working with single-board computers such as Raspberry Pi, Jetson, Orange Pi, BeagleBone, or Coral Dev Board.
Safety Rules
- Do not run destructive shell commands.
- Ask before installing services, changing boot behavior, or modifying system packages.
- Do not expose secrets in logs.
- Prefer dry-run commands first.
- Preserve deployment logs.
Workflow
- Identify target host.
- Check SSH connectivity.
- Inspect OS, architecture, Python, Docker, and required runtime.
- Copy or pull project code.
- Install dependencies with approval if needed.
- Run service manually first.
- Inspect logs.
- Verify health check or expected output.
- Ask before installing persistent systemd service.
- Summarize deployment status.
Preferred Commands
ssh target "uname -a"
ssh target "python3 --version"
ssh target "docker --version"
ssh target "systemctl status service-name"
ssh target "journalctl -u service-name -n 100 --no-pager"
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.
- 6d ago First seen · 42 lines · 53 tokens per session scan A 6d261daeb78e
sbc-deploy is a skill published in the GitHub repository jl-codes/platformio-mcp (50 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 286 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-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
google-cloud-filestore-autoscale
Inspects Google Cloud Filestore capacity and utilization, evaluates storage scaling rules, and performs capacity autoscaling (scale UP for low free space or scale DOWN for cost optimization). Use when monitoring Filestore instance headroom, resizing instance shares, configuring automated growth/shrink thresholds…
doca-hardware-safety
Use this skill whenever the agent is about to recommend or apply a change that touches DPU / NIC hardware state on a live system — mlxconfig firmware-parameter write, NIC firmware burn, BFB reflash, NIC ↔ DPU mode flip, SR-IOV or device-emulation slot enable, kernel boot-parameter change (IOMMU, hugepages, VFIO), PCIe…
aws-lambda-microvms
Builds, runs, debugs, and operates applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments running inside a container with up to 8 hr lifetimes. Applicable when workloads need strong isolation between tenants, isolated serverless compute, sandbox compute, or…
doca-setup
Use this skill when the user is dealing with the DOCA environment around their workload — verifying an install is healthy, preparing the build env (pkg-config, headers, LDLIBRARYPATH, hugepages, devlink, representors), debugging env-class failures, deciding container-vs-bare-metal deployment shape, or reaching a DOCA…
doca-upgrade
Use this skill when the user is contemplating a DOCA upgrade or downgrade — moving a host to a newer DOCA release, refreshing the BlueField BFB, bumping the NGC DOCA container tag, or rolling back. The discipline is detect → report → ASK → only-then guided upgrade: detect what is installed, discover what newer release…