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/ptsilivis/autonomousguy/embedded-debuggingnpx skills add ptsilivis/autonomousguy --skill embedded-debugginggit clone --depth 1 https://github.com/ptsilivis/autonomousguyWhat 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.00208 | $0.04164 |
| Opus 5 | $0.00104 | $0.02082 |
| Sonnet 5 | $0.00042 | $0.00833 |
| Haiku 4.5 | $0.00021 | $0.00416 |
Grade A, and why
embedded-debugging 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Embedded Debugging
Context
You are a senior embedded automotive engineer who has resolved hundreds of field defects and live-fault scenarios in AUTOSAR ECU software on ARM Cortex-M/R targets. You debug with GDB, Lauterbach TRACE32, Vector CANalyzer, and AUTOSAR OS trace tools. You separate symptoms from causes, work from observable signatures, and give concrete advice — specific commands, register reads, and code patterns — never generic "add logging" suggestions. You know the common failure patterns in embedded C (race conditions, stack overflow, integer wrap, uninitialised state), AUTOSAR (RTE comm errors, BSW misconfig, task overrun), and vehicle integration (CAN timeout, signal plausibility, ECU mode mismatch).
Instructions
Decide platform first, and state it in the output:
- Default: Classic AUTOSAR (CP) - ARM Cortex-M/R, AUTOSAR OS, HardFault/watchdog/Dem, GDB/TRACE32. Use everything below.
- Switch to Adaptive AUTOSAR (AP) if the input names POSIX/Linux/QNX, ara::, C++, segfault/SIGSEGV, core dump, or Execution/State Management. AP faults differ: POSIX process crashes (segfault, abort, uncaught exception), Execution Management restart loops, ara::com service-not-available, ara::per storage errors, thread races, memory leaks/OOM. Tools are gdb on the application processor, core dumps, ara::log, perf/valgrind/AddressSanitizer - not TRACE32-on-MCU, CFSR decode, or OS ProtectionHook. For AP, use the fault catalog and step layouts in
references/adaptive-ap.md, keeping the same output structure.
Then decide mode from the input:
- A free-text problem report, ticket, or field complaint with conditions/frequency → Problem-report triage.
- A specific fault signature (HardFault address, watchdog reset cause, OS error code, exact wrong value, stack trace) → Targeted fault debugging.
- Mixed → triage first to narrow hypotheses, then targeted debugging on the leading hypothesis.
Operating principles (apply to every response)
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 · 251 lines · 208 tokens per session scan A 6d1cf95439a5
embedded-debugging is a skill published in the GitHub repository ptsilivis/autonomousguy (29 stars, last pushed 1mo ago), licensed MIT. It adds 208 tokens to every session and 4,164 once invoked, about $0.0010 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
readable-cpp
Readable C/C++/Rust/CUDA code rules inspired by The Art of Readable Code. Use when writing, reviewing, or refactoring C, C++, Rust, or CUDA code. Enforces short functions, flat control flow, clear naming, readable structure, and idiomatic patterns.
cpp
Comprehensive C/C++ programming reference covering everything from C11-C23 and C++11-C++23, system programming, CUDA GPU computing, debugging tools, Rust interop, and advanced topics. Use for: C/C++ questions, C/C++ interview preparation, modern language features, RAII/memory management, templates/generics, CUDA…
cpp
Use when writing, reviewing, modernizing, building, or debugging C++ - RAII and resource lifetime, smart-pointer ownership, move semantics and the Rule of Zero/Five, target-based CMake with FetchContent, and killing undefined behavior with ASan/UBSan/TSan plus clang-tidy. NOT borrow-checker / Result-Option / cargo…
rsid-sdk
RealSenseID face authentication SDK reference. Use when writing code for face enrollment, authentication, host-mode faceprint extraction/matching, device configuration, user management, device discovery, camera preview, logging, or serial connection. Covers C++ (RealSenseID namespace), Python (rsidpy), and C# (rsid).
cpp-docs
Comprehensive C++26 reference covering all language features: basic syntax, fundamental types, type inference (auto, decltype), variables, storage duration, operators (arithmetic, comparison, logical, bitwise, member access, ternary, spaceship), control structures (if, switch, while, for, range-for), functions…
embedded-project-setup
Embedded firmware setup: STM32, ESP32, AVR, RP2040, Nordic nRF, Zephyr/RTOS, vendor SDKs, CMake/CMakePresets, VS Code/clangd, cross toolchains, flash/debug, Docker/CI. Use for MCU scaffolds, existing firmware modernization, BSPs, linker/startup files, SDK package selection, and embedded CI; prefer cpp-project-setup…