Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/athitupakan/garmin-dev-skillsnpx agentmods add commands/athitupakan/garmin-dev-skills/buildWrote 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/commands/athitupakan/garmin-dev-skills/build)<a href="https://agentmods.dev/commands/athitupakan/garmin-dev-skills/build"><img src="https://agentmods.dev/badge/commands/athitupakan/garmin-dev-skills/build.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.00000 | $0.00274 |
| Opus 5 | $0.00000 | $0.00137 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
build 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 7d 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
Build (compile only)
Compile source\ + resources\ → bin\<project>.prg. Does NOT launch simulator or push.
Run
# Windows
.\.claude\skills\garmin-dev\scripts\windows\build.ps1
# macOS / Linux
./.claude/skills/garmin-dev/scripts/posix/build.sh
Use when
- Checking that code compiles after an edit
- Simulator already running; you'll push manually with
monkeydoorrun.ps1 - CI / pre-commit check (exit code 0 = success)
Expected outcome
- Stdout:
BUILD SUCCESSFUL $LASTEXITCODE= 0bin\<project>.prgupdated mtime (project name comes frommanifest.xmlparent folder —_envauto-detects it)
On failure
'java' is not recognized—_env.ps1JDK path wrong; see ../troubleshooting.mdBUILD FAILEDwith parse/type errors — fix source, re-run- Other unexpected errors → ../troubleshooting.md
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.
- 7d ago First seen · 34 lines · 0 tokens per session scan A 99a220237d1f
build is a command published in the GitHub repository athitupakan/garmin-dev-skills (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 274 tokens. 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.
Other commands, from other repositories
scope
A command for connecting to supported oscilloscopes, capturing or reading waveforms, measuring them, and saving results as CSV files or plots. An oscilloscope is a device that displays changing electrical signals.
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.
svd
A command-line tool that reads CMSIS-SVD files, which describe a chip's peripherals, registers, and bit fields. It can list register addresses and decode the current register values while the device is running.
map
A parser for Keil compiler map files, which are build reports describing where program code and data are placed in memory. It reports object sizes, memory regions, symbols, and stack or heap details.
size
A command that reads a Keil compiler .map file, a build report describing where firmware uses memory. It reports Flash, RAM, stack, and heap allocation and compares usage with warning limits.