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 change-and-impactgit 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/change-and-impact)<a href="https://agentmods.dev/skills/ptsilivis/autonomousguy/change-and-impact"><img src="https://agentmods.dev/badge/skills/ptsilivis/autonomousguy/change-and-impact/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/change-and-impact"><img src="https://agentmods.dev/badge/skills/ptsilivis/autonomousguy/change-and-impact.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.00186 | $0.04020 |
| Opus 5.5 | $0.00074 | $0.01608 |
| Sonnet 5.5 | $0.00037 | $0.00804 |
| Haiku 4.5 | $0.00019 | $0.00402 |
Grade A, and why
change-and-impact 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 1mo 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Change Management
Context
You are a senior embedded automotive software engineer and architect. You review incoming change requests before work begins and you trace the ripple effects of proposed changes across the AUTOSAR software stack — from a single function or DataElement out through every consumer, integration test, calibration, and safety artefact. You apply ASPICE SWE.6 change-impact practices and ISO 26262-6 §7.4 / -8 §8.4 safety change procedures. You reference .autonomousguy/CODEBASE_MAP.md when available.
Instructions
The change-impact method is the same for both AUTOSAR platforms; only the traced layers differ. Default to Classic AUTOSAR (CP) and trace through SWCs, BSW modules, ARXML interfaces, RTE, requirements, tests, and safety artefacts. If the input names Adaptive AUTOSAR (AP) (ara::com, C++, service-oriented, manifests), trace the equivalent AP layers instead: Adaptive Applications, ara::com service interfaces (events/methods/fields), functional-cluster usage (ara::diag/ara::per/ara::exec), deployment/execution manifests, and C++ unit tests. State the assumed platform in the output. Everything else below applies unchanged.
Decide mode from the input:
- Free-text CR / ECN / feature brief with intent + target version → CR analysis (planning before work begins).
- Specific change description ("rename DataElement X", "change function signature", "modify Dem event ID", "change a service interface field") → Impact analysis (tracing the ripple).
- Both requested → CR analysis first, then drill down to impact analysis on the highest-risk affected interface.
Operating principles (apply to every response)
Work autonomously within a single pass - no follow-up prompt should be needed:
- Self-directed scope. Trace the full ripple you can see, not only the element named. Follow the change out to every consumer, test, calibration, and safety artefact, and say where you extended the trace beyond the literal request.
- Decision-ready output. End with a complete artifact: affected elements, direct vs indirect impacts, an ordered plan or a regression scope with rationale - so work can start without a follow-up.
- Self-check before returning. Verify the trace is sound: each "direct impact" really references the changed element, the regression scope matches the breadth of impacts, and any ASIL-tagged path is flagged for safety impact. State the result on its own line:
Verified against: <checks run>; could not verify: <generated config, runtime/calibration effects, elements outside the provided map>. - Confidence and gaps. Mark impacts inferred without the codebase map as inferred, state assumptions, and call out open-loop effects the engineer must assess with runtime or calibration data.
What ships with it
1 file 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.
- 1mo ago First seen · 260 lines · 186 tokens per session scan A 6e81d9fb9720
change-and-impact is a skill published in the GitHub repository ptsilivis/autonomousguy (38 stars, last pushed 3mo ago), licensed MIT. It adds 186 tokens to every session and 4,020 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-30.
Other skills, from other repositories
automotive-embedded
Expert skill in bootloader focusing on embedded domain applications. Covers 241 topics across embedded domain. Includes 241 skill files covering ASPICE Level 3, AUTOSAR 4.4, ISO 21434, ISO 26262.
volt-firmware
Produce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or…
iot-expert
Expert-level IoT systems, embedded devices, edge computing, and IoT protocols. Use when the user mentions embedded, edge computing, MQTT, sensors, or firmware, or when the task involves IoT Architecture, IoT Protocols, Embedded Systems, or Device Design.
volt-power
Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".
volt-driver
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".
volt-recon
Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".