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 AISEE-LAB/aisee-plugin --skill hw-change-plangit clone --depth 1 https://github.com/AISEE-LAB/aisee-pluginWrote 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/aisee-lab/aisee-plugin/hw-change-plan)<a href="https://agentmods.dev/skills/aisee-lab/aisee-plugin/hw-change-plan"><img src="https://agentmods.dev/badge/skills/aisee-lab/aisee-plugin/hw-change-plan.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.00127 | $0.02028 |
| Opus 5 | $0.00063 | $0.01014 |
| Sonnet 5 | $0.00025 | $0.00406 |
| Haiku 4.5 | $0.00013 | $0.00203 |
Grade A, and why
hw:change-plan 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 8d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hw:change-plan
把硬件整体输入拆成多个可执行的 OpenSpec changes。每个 change 应使用 aisee-device-spec-driven,除非用户明确选择其他 schema。
本技能参考 aisee:change-plan 的边界规划方式,但针对硬件/嵌入式项目增加 HW / FW / RT / VER 追踪。
Inputs
必需:
aisee/docs/requirements/*-hw-srs.mdaisee/docs/architecture/*-hw-architecture.md
可选:
docs/modules/*.mddocs/project-structure.mddocs/clock-contract.mddocs/memory-device-contract.mdhw:init scan-existing的只读扫描摘要- 现有 OpenSpec active changes
可选参数:
--strategy vertical|risk|parallel,默认vertical--granularity fine|medium|coarse,默认medium--schema <name>,默认aisee-device-spec-driven--max-changes <N>,默认8--single-if-small
References
需要拆分规则时读取:
references/change-boundary-rules.md
生成文档时读取:
assets/change-plan-template.md
Output
保存到:
aisee/docs/change-plan/<YYYY-MM-DD>-<slug>-hw-change-plan.md
输出必须包含:
- Summary
- Dependency graph
- Change details
- 每个 change 的 schema,默认
aisee-device-spec-driven - 每个 change 的 In Scope / Out of Scope
- 每个 change 的 Source-map seed:FR / HW / FW / RT / VER
- 每个 contract artifact 的适用性:hardware / firmware / runtime / verification
- Depends on / Parallel with
- Change rationale
- Copy-ready
/opsx:new "<change>" --schema aisee-device-spec-driven命令 - 整体拆分依据和
[ASSUMPTION]/[RISK]/[ARCH-BLOCKER]
Phase 0 - Read Project Context
PowerShell:
Get-Content -ErrorAction Stop aisee/docs/requirements/*-hw-srs.md
Get-Content -ErrorAction Stop aisee/docs/architecture/*-hw-architecture.md
Get-Content -ErrorAction SilentlyContinue docs/modules/*.md
Get-Content -ErrorAction SilentlyContinue docs/project-structure.md
Get-Content -ErrorAction SilentlyContinue docs/clock-contract.md
Get-Content -ErrorAction SilentlyContinue docs/memory-device-contract.md
cmd /c openspec list --json 2>nul
cmd /c openspec schemas --json 2>nul
POSIX shell:
cat aisee/docs/requirements/*-hw-srs.md
cat aisee/docs/architecture/*-hw-architecture.md
cat docs/modules/*.md 2>/dev/null
cat docs/project-structure.md 2>/dev/null
cat docs/clock-contract.md 2>/dev/null
cat docs/memory-device-contract.md 2>/dev/null
openspec list --json 2>/dev/null
openspec schemas --json 2>/dev/null
What ships with it
4 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.
- 8d ago First seen · 194 lines · 127 tokens per session scan A acd000c73b84
hw:change-plan is a skill published in the GitHub repository AISEE-LAB/aisee-plugin (11 stars, last pushed 2mo ago), licensed MIT. It adds 127 tokens to every session and 2,028 once invoked, about $0.0006 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
camsnap
Capture frames or clips from RTSP/ONVIF cameras. Grabs snapshots, video clips, and motion events from IP cameras, security cameras, and video streams. Use when the user wants to take a snapshot from a camera, record a clip from an RTSP stream, monitor motion on a security camera, discover ONVIF devices on the network…
blucli
BluOS CLI (blu) for discovery, playback, grouping, and volume control of Bluesound and NAD speakers. Use when the user wants to play music, stream audio, control speakers, adjust volume, group or ungroup Bluesound players, search TuneIn radio, or manage multi-room streaming setups.
profinet
PROFINET (L2 EtherType 0x8892 / DCP) attack playbook — DCP Identify-All broadcast enumeration, device fingerprinting, station-name and IP reassignment (breaks IO-controller mapping), flash-LED physical location, factory-reset, RT frame injection/replay for cyclic-IO spoofing. Siemens/EU fieldbus peer of S7Comm…
opentrons-integration
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
pylabrobot
Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API…
omh-physical-device-readiness
This is a Hermes-native physical-device-readiness workflow skill.