SkillsBench is a benchmark for measuring how effectively AI agents use modular skills—folders containing instructions, scripts, and resources—to complete specialized tasks. It helps researchers and developers evaluate both skill quality and agent behavior, including tasks that require combining multiple skills. The catalogue’s skills and instructions are evaluated as part of this workflow.
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 benchflow-ai/skillsbench --skill excitation-signal-designgit clone --depth 1 https://github.com/benchflow-ai/skillsbenchWrote 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/benchflow-ai/skillsbench/excitation-signal-design)<a href="https://agentmods.dev/skills/benchflow-ai/skillsbench/excitation-signal-design"><img src="https://agentmods.dev/badge/skills/benchflow-ai/skillsbench/excitation-signal-design/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/benchflow-ai/skillsbench/excitation-signal-design"><img src="https://agentmods.dev/badge/skills/benchflow-ai/skillsbench/excitation-signal-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00551 |
| Opus 5 | $0.00012 | $0.00275 |
| Sonnet 5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
excitation-signal-design 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- excitation-signal-design — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Excitation Signal Design for System Identification
Overview
When identifying the dynamics of an unknown system, you must excite the system with a known input and observe its response. This skill describes how to design effective excitation signals for parameter estimation.
Step Test Method
The simplest excitation signal for first-order systems is a step test:
- Start at steady state: Ensure the system is stable at a known operating point
- Apply a step input: Change the input from zero to a constant value
- Hold for sufficient duration: Wait long enough to observe the full response
- Record the response: Capture input and output data at regular intervals
Duration Guidelines
The test should run long enough to capture the system dynamics:
- Minimum: At least 2-3 time constants to see the response shape
- Recommended: 3-5 time constants for accurate parameter estimation
- Rule of thumb: If the output appears to have settled, you've collected enough data
Sample Rate Selection
Choose a sample rate that captures the transient behavior:
- Too slow: Miss important dynamics during the rise phase
- Too fast: Excessive data without added information
- Good practice: At least 10-20 samples per time constant
Data Collection
During the step test, record:
- Time (from start of test)
- Output measurement (with sensor noise)
- Input command
# Example data collection pattern
data = []
for step in range(num_steps):
result = system.step(input_value)
data.append({
"time": result["time"],
"output": result["output"],
"input": result["input"]
})
Expected Response Shape
For a first-order system, the step response follows an exponential curve:
- Initial: Output at starting value
- Rising: Exponential approach toward new steady state
- Final: Asymptotically approaches steady-state value
The response follows: y(t) = y_initial + K*u*(1 - exp(-t/tau))
Where K is the process gain and tau is the time constant.
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 · 73 lines · 24 tokens per session scan A 2a95543b6a10
excitation-signal-design is a skill published in the GitHub repository benchflow-ai/skillsbench (1,764 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 551 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-09-03.
Other skills, from other repositories
ruview-applications
Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
calibrate-room
Run the ADR-151 per-room calibration pipeline — baseline → enroll → extract → train → a bank of small specialists (presence/posture/breathing/heartbeat/restlessness/anomaly).
i4h-catheter-navigation
Overview of workflows/catheternavigation/ (fluorosim DRR, XPBD physics, vasculature digital twin). Use when the user asks what the catheter navigation workflow is, what's supported, or where to start.
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…