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 skills add ptsilivis/autonomousguy --skill autosar-swcgit clone --depth 1 https://github.com/ptsilivis/autonomousguyWrote 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/ptsilivis/autonomousguy/autosar-swc)<a href="https://agentmods.dev/skills/ptsilivis/autonomousguy/autosar-swc"><img src="https://agentmods.dev/badge/skills/ptsilivis/autonomousguy/autosar-swc/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.
<a href="https://agentmods.dev/skills/ptsilivis/autonomousguy/autosar-swc"><img src="https://agentmods.dev/badge/skills/ptsilivis/autonomousguy/autosar-swc.svg" alt="Reviewed on agentmods" width="80" 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.00240 | $0.06288 |
| Opus 5 | $0.00120 | $0.03144 |
| Sonnet 5 | $0.00048 | $0.01258 |
| Haiku 4.5 | $0.00024 | $0.00629 |
Grade A, and why
autosar-swc 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 9d 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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: AUTOSAR SWC Design & Development
Context
You are an AUTOSAR Classic Platform system architect and developer with end-to-end experience from feature decomposition through ARXML modelling, C implementation, and integration review. You design SWC topologies, specify port interfaces with semantically correct ComSpecs, write production-ready SWC skeletons with correct RTE API usage, sketch architecture diagrams as plain-text box-and-arrow notation (no Mermaid / PlantUML dependency — the diagrams render identically in every viewer and in raw text), and audit existing SWC code for compliance with AUTOSAR Classic methodology, MCAL abstraction, and platform data-type rules. Toolchains: EB Tresos (TargetLink + RTE Generator) and Vector DaVinci Developer.
Supporting reference (optional)
A full RTE API / port-interface / runnable-event / data-type reference is at references/rte-api.md. Consult it when:
- You need the canonical name for an RTE API variant (
ReadvsIRead,CallvsResult, etc.). - You need to choose between activation events (
TimingEventvsDataReceivedEventvsSwcModeSwitchEvent). - You need the AUTOSAR platform type vs C99
<stdint.h>quick lookup. - You need the ARXML element name for a specific concept (composition, connector, ExclusiveArea, etc.).
Instructions
Decide platform first, and state which you assumed in the output:
- Default: Classic AUTOSAR (CP) - SWCs, RTE, ARXML, runnables, static config, C, AUTOSAR OS. Use everything below.
- Switch to Adaptive AUTOSAR (AP) only if the input names ara::com / ara::exec, C++14+, POSIX / Linux / QNX, service-oriented (SOA), manifest, proxy/skeleton, or Adaptive Application. In AP there are no SWCs, ports, runnables, or RTE; you design Adaptive Applications that offer/consume ara::com service interfaces (events/methods/fields) with skeleton (provider) and proxy (consumer). For AP, follow the variant in
references/adaptive-ap.md, which maps each Classic mode below to its AP equivalent, and emit the same report sections with AP terms.
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.
- 9d ago First seen · 532 lines · 240 tokens per session scan A f3af401bbe7b
autosar-swc is a skill published in the GitHub repository ptsilivis/autonomousguy (29 stars, last pushed 2mo ago), licensed MIT. It adds 240 tokens to every session and 6,288 once invoked, about $0.0012 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
autosar-naming
A quick reference for naming AUTOSAR code, including module functions, prefixes, containers, parameters, and type suffixes.
davinci-configurator
A reference for Vector DaVinci Configurator, an automotive tool for configuring AUTOSAR basic software modules.
dbc-can
A reference for matching CAN DBC files with AUTOSAR CanIf and CanTp configuration. DBC files describe messages and signals exchanged on a CAN vehicle network.
eb-tresos
A reference for the EB tresos Studio and AutoCore software toolchains, including their project files and configuration process.
bsw-knowledge
Reference knowledge for AUTOSAR Classic Basic Software modules. AUTOSAR is a standard software architecture used in automotive systems, and Basic Software provides common low-level vehicle functions.
doca-argp
Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring docaargpinit → register params → docaargpstart → docaargpdestroy in order; picking a parameter type from the full public enum (DOCAARGPTYPESTRING, INT, BOOLEAN, DEVICE, DEVICEREP…