Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeic/vibe-icnpx agentmods add skills/vibeic/vibe-ic/field-agent-loopWrote 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/vibeic/vibe-ic/field-agent-loop)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/field-agent-loop"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/field-agent-loop.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 185 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00211 | $0.10661 |
| Opus 5 | $0.00105 | $0.05331 |
| Sonnet 5 | $0.00042 | $0.02132 |
| Haiku 4.5 | $0.00021 | $0.01066 |
Grade A, and why
field-agent-loop 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 — 832 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case-study notation. This skill cites the IC-A / USB-HID tester / MDV-A1101 BENCH-A reference project as concrete evidence for the rules below. The rules themselves are chip-AGNOSTIC and apply to any IC of the matching
ic_class(seevibe-ic-marketplace/plugins/vibe-ic/programs/ic_class_profile.py). When you adopt this skill on a different IC, swapIC-A→<your IC name>andUSB-HID tester→<your host-tester name>; the structural gates and rule bodies do not depend on those SKUs. Seedocs/design/CASE_STUDIES/IC-A_*.mdfor the full BENCH-A regression history.
Field-Agent Loop — Closed-Loop Plugin Quality Improvement
Purpose
The field-agent is the organic improvement engine for the vibe-ic plugin. It treats real IC benchmark projects as a test harness: re-run the plugin at HEAD, ask a fresh LLM to compare source docs against generated output, and convert every systematic gap it finds into a structured backlog issue.
Contribution-layer note. The field-agent is a Layer-1 intake role: it files a backlog (a report — or hands the gatekeeper a candidate-patch bundle) and audits landed fixes. It never edits the plugin/MCP and never pushes to
main. Direct-push is the maintainer-internal (Layer-2) landing method for the gatekeeper's own fixes — not the field-agent's path. The maintainer resolves every backlog into the next plugin version.
The core-agent now self-verifies and CLOSES each issue it
fixes (adding the core-closed label). The default terminal
state is therefore CLOSED. The field-agent is the
audit/reopen safety net: at every cron tick it re-checks the
core-agent's closed issues on the actual benchmark — not on the
unit test fixtures. If the fix holds on real silicon it stamps
field-verified (terminal); if it does not, the field-agent
reopens the issue (gh issue reopen), posts counter-evidence,
and removes core-closed so the core-agent re-engages. This
audit/reopen model is what kills the old wait-for-verification
limbo where a fixed issue sat un-confirmed forever.
What ships with it
3 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 · 832 lines · 211 tokens per session scan A 4867cc7c1fe8
field-agent-loop is a skill published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It adds 211 tokens to every session and 10,661 once invoked, about $0.0011 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
analog-verify
Pre-simulation review and Spectre simulation verification for analog circuits. Reviews circuit netlist and testbench, runs simulation, produces margin report. Use after analog-design completes a netlist.
step6-verify
Step 6 · Per-module simulation verification (amnesia audit → human-confirmed plan → autonomous local-fix loop → full re-verify; escalate only when local options are exhausted).
boardrepo
Read and review real PCB projects on BoardRepo. Search published hardware designs, open a board's schematic connectivity, bill of materials and files, run KiCad's DRC and ERC, and check a design against a fabrication house's limits. Use whenever the user names a BoardRepo board or URL, asks to find a published board…
analog-netlist-crawl
Crawl and analyze post-layout parasitic netlists without running SPICE. Answers "what's the effective resistance from node A to node B across this massive R mesh?", "inside the VREFN mesh, which device pins are electrically farthest apart?", "which nets have the worst coupling?", "where does settling bottleneck?" — by…
analog-design
Transistor-level circuit design for one analog sub-block. Produces Spectre netlist with hand-calculation rationale. Use when designing a specific circuit block after architecture is defined.
analog-pipeline
MANDATORY — MUST load this skill when the user mentions: OTA, ADC, PLL, comparator, bandgap, LDO, amplifier, opamp, or any analog/mixed-signal IC design task. Full analog design pipeline: spec -> architecture -> design -> verify -> deliver. Orchestrates analog-decompose, analog-behavioral, analog-design…