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 agodianel/esp32-claude-workbench --skill feature_contractgit clone --depth 1 https://github.com/agodianel/esp32-claude-workbenchWrote 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/agodianel/esp32-claude-workbench/feature_contract)<a href="https://agentmods.dev/skills/agodianel/esp32-claude-workbench/feature_contract"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/feature_contract/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/agodianel/esp32-claude-workbench/feature_contract"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/feature_contract.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.00019 | $0.00656 |
| Opus 5 | $0.00010 | $0.00328 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
feature_contract 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Contract
Generate an implementation contract that must be reviewed and approved before any code changes begin.
When to Use
- Before implementing any feature or bug fix.
- Before refactoring existing code.
- Before making any architecture changes.
- Always. No exceptions.
Steps
1. Gather Requirements
Ask or determine:
- What is the requested change?
- What is the expected behavior after the change?
- What board/target is this for?
- Are there hardware constraints?
2. Define Scope
Document:
- Summary: One-paragraph description of the change.
- Non-goals: What this change explicitly does NOT do.
- Affected files: List every file that will be created, modified, or deleted.
- APIs touched: Public functions or interfaces that will change.
3. Assess Risks
Evaluate:
- Concurrency risks: Shared state, race conditions, task interactions.
- Peripheral risks: Pin conflicts, bus contention, timing issues.
- Memory risks: Heap impact, stack requirements, DMA buffers.
- Boot risks: Changes that affect boot sequence or strapping pins.
- Backward compatibility: Breaking changes to APIs or protocols.
4. Define Test Plan
Specify:
- New tests to add: Unit tests, integration tests, or validation scripts.
- Existing tests to update: Tests affected by the change.
- Manual verification: Steps for hardware testing if applicable.
- Test evidence required: What output proves the change works.
5. Define Rollback Strategy
Document:
- How to revert the change.
- What state needs to be restored.
- Any data migration or NVS implications.
6. Generate Contract Document
Write the contract to the active mission file or as a standalone document using the template at missions/templates/implementation_contract.md.
Contract Template
# Implementation Contract
## Change Summary
[One-paragraph description]
## Non-Goals
- [What this does NOT include]
## Affected Files
| File | Action | Description |
|------|--------|-------------|
| path/to/file.c | MODIFY | [What changes] |
| path/to/new.h | CREATE | [Purpose] |
## APIs Touched
- `function_name()` — [How it changes]
## Risk Assessment
### Concurrency: [LOW/MED/HIGH]
[Details]
### Peripheral: [LOW/MED/HIGH]
[Details]
### Memory: [LOW/MED/HIGH]
[Details]
## Test Plan
- [ ] [Test case description]
## Rollback Strategy
[Steps to revert]
## Acceptance Criteria
- [ ] [Criterion]
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 · 109 lines · 19 tokens per session scan A ae5eea82370e
feature_contract is a skill published in the GitHub repository agodianel/esp32-claude-workbench (79 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 656 once invoked, about $0.0001 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.