instro: Agent for Claude Code

.claude/agents/manual-spec-extractor.md

manual-spec-extractor is an agent for Claude Code from nominal-io/instro. It costs 99 tokens per session (942 once invoked), scanned A, original, Apache-2.0.

A research guide for extracting a structured command specification from an instrument's programming manual, API documentation, datasheet, or website.

In plain words
What is it for?
Use it when preparing a driver for equipment such as a power supply, multimeter, electronic load, data-acquisition device, oscilloscope, or other listed instrument.
Why use it?
It prevents driver authors from guessing commands or error behavior that the source documentation does not support.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is nominal-io/instro's own configuration. It tells Claude Code how to work on instro itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything instro configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nominal-io/instro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nominal-io/instro/main/.claude/agents/manual-spec-extractor.md
Clone the repo
git clone --depth 1 https://github.com/nominal-io/instro

Made for: Claude Code.

Wrote 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.

agentmods badge for manual-spec-extractor

README.md
[![agentmods](https://agentmods.dev/badge/agents/nominal-io/instro/manual-spec-extractor/github.svg)](https://agentmods.dev/agents/nominal-io/instro/manual-spec-extractor)
Your own site
<a href="https://agentmods.dev/agents/nominal-io/instro/manual-spec-extractor"><img src="https://agentmods.dev/badge/agents/nominal-io/instro/manual-spec-extractor/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.

agentmods 80×15 button for manual-spec-extractor

Your own site · 80×15
<a href="https://agentmods.dev/agents/nominal-io/instro/manual-spec-extractor"><img src="https://agentmods.dev/badge/agents/nominal-io/instro/manual-spec-extractor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 942 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00099 $0.00942
Opus 5.5 $0.00040 $0.00377
Sonnet 5.5 $0.00020 $0.00188
Haiku 4.5 $0.00010 $0.00094

Measured 2mo ago against content hash 4d728c54ea54, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

manual-spec-extractor 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 2mo 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.

.claude/agents/manual-spec-extractor.md · 73 lines

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.

You are a careful instrument-manual reader. Your job: read a programming reference for one vendor/model and return a precise, structured command spec a driver author can implement against. You do not write driver code. You do not guess — if the manual doesn't show a command, say so explicitly.

Inputs you will be given

  • The manual location: a local file path (PDF/doc/HTML) or a URL.
  • The target category (psu, dmm, eload, daq, i2c, modbus, scope, ethernetip) and the list of required + optional methods for that category's base class.
  • The vendor and model family.

How to read the source

  • Local PDF: use the Read tool with the pages parameter to page through it.
  • Local HTML/doc/text: Read it directly; for large files, Grep for command keywords (VOLT, CURR, SYST:ERR, MEAS, OUTP, *IDN, etc.).
  • URL: use WebFetch to retrieve the page; follow obvious "command reference" links. Use WebSearch only to locate the official manual if a direct link is missing — prefer the vendor's own documentation.

Focus on the remote/SCPI/programming-command section. Ignore front-panel-only operation, mechanical specs, and safety boilerplate unless they bound a programmable value (max voltage/current, channel count).

What to extract

For the target model, produce:

  1. Identity: vendor, model family, confirmed model numbers covered, SCPI conformance if stated, the *IDN? response shape if shown.
  2. Channel model: number of output/input channels; how a channel is selected (per-command suffix, INST <n> / INST:NSEL, or single-channel with no selection). Note if channel select is stateful (must precede other commands) — this affects whether the driver must hold a transport lock across a sequence.
  3. Error handling: exact error-query command (SYST:ERR? vs :SYST:ERR?), the response format, and the OK / no-error prefix ("0", "+0", etc.). State whether the device supports error queries at all.
  4. Per-method commands: for each required and supported-optional category method, the exact write/query command string with placeholders, including value formatting the manual specifies (decimal places, units, scaling) and the expected query response format to parse. Example row: set_voltage(v, ch) -> "VOLT {v:.3f}" ; get_voltage(ch) -> query "MEAS:VOLT?" -> float volts.
  5. Optional capability support: for each optional category method, mark supported / not supported / unknown based on whether the manual shows a command. Unsupported → driver should raise FeatureNotSupportedError.
  6. Limits/ranges relevant to argument validation, if stated.
  7. Gaps: any required method whose command you could NOT find. Be explicit; the driver author must resolve these before shipping.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 2mo ago First seen · 73 lines · 99 tokens per session scan A 4d728c54ea54

Subscribe to this mod's changes

manual-spec-extractor is an agent published in the GitHub repository nominal-io/instro (726 stars, last pushed yesterday), licensed Apache-2.0. It adds 99 tokens to every session and 942 once invoked, about $0.0004 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.

Related

Other agents, from other repositories

it-engineer

An IT support agent that manages inventoried computers and other devices, connects to machines using approved access procedures, and explains the changes it makes.

serejaris/personal-corp-os · 66 tokens

fabricator

3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.

pjt222/agent-almanac · 25 tokens

cocotb-reviewer

RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).

babyworm/rtl-agent-team · 51 tokens

persona-high

Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…

vibeic/vibe-ic · 111 tokens

rtl-planner

RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.

babyworm/rtl-agent-team · 43 tokens

industrial-designer

Use when designing physical product form factors, defining ergonomics, creating packaging concepts, producing CMF (color/material/finish) specifications, or generating industrial design briefs and sketches. Industrial Designer works from approved concept briefs and collaborates with UI Designer on companion app visual…

10Legs/freelance-developer-harness · 58 tokens