fpga-development

fpga-development is a skill for Claude Code, Codex from magnus919/agent-skills. It costs 97 tokens per session (1,959 once invoked), scanned A, original, MIT.

A guide to designing and verifying FPGA logic, where programmable chips implement hardware behavior described in a hardware language.

In plain words
What is it for?
Use it for synthesizable HDL, fixed-point arithmetic, handshakes, testbenches, timing constraints, clock-domain crossing analysis, timing closure, and FPGA bring-up.
Why use it?
It helps catch errors in clocks, resets, signal crossings, timing, resource use, and hardware interfaces that ordinary software testing may miss.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for synthesizable HDL, fixed-point arithmetic, handshakes, testbenches, timing constraints, clock-domain crossing analysis, timing closure, and FPGA bring-up.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/magnus919/agent-skills/fpga-development
Install

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.

Any agent
npx skills add magnus919/agent-skills --skill fpga-development
Clone the repo
git clone --depth 1 https://github.com/magnus919/agent-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin fpga-development — /plugin install fpga-development after adding the marketplace above.

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 fpga-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/magnus919/agent-skills/fpga-development/github.svg)](https://agentmods.dev/skills/magnus919/agent-skills/fpga-development)
Your own site
<a href="https://agentmods.dev/skills/magnus919/agent-skills/fpga-development"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/fpga-development/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 fpga-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/magnus919/agent-skills/fpga-development"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/fpga-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,959 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.00097 $0.01959
Opus 5.5 $0.00039 $0.00784
Sonnet 5.5 $0.00019 $0.00392
Haiku 4.5 $0.00010 $0.00196

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

Security

Grade A, and why

fpga-development 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/fpga_fixture.py, scripts/test_fixture.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

fpga-development/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

FPGA Development

Treat HDL as a description of concurrent hardware with explicit temporal and electrical interfaces. A correct design requires consistent functional intent, language semantics, clock/reset behavior, implementation constraints and verification evidence. Compilation, simulation, synthesis, timing and physical observation establish different facts.

Operating contract

  1. Identify the requested decision and design boundary: new RTL, review, simulation failure, resource problem, CDC/timing analysis, implementation or hardware release. Use the smallest complete evidence set for that decision.
  2. Record device/package, board revision, clocks, reset, I/O voltage and pin constraints before making target-specific claims. Pure RTL reasoning can proceed from a stated abstract interface without inventing a board.
  3. State transaction semantics, latency, throughput, backpressure, loss/duplication policy, initialization and arithmetic behavior before implementation. A waveform picture is not an interface contract.
  4. Keep synthesizable design and verification-only constructs separate. Match the HDL subset and vendor primitive model to the actual simulator and synthesizer versions.
  5. Review constraint coverage and exception intent before interpreting slack. A green summary with missing clocks or unconstrained endpoints is incomplete evidence.
  6. Before programming, resetting, erasing or otherwise changing connected hardware, confirm the target, scope, and rollback path before acting. Read-only discovery may proceed without confirmation. Bitstreams and programming paths must match the exact target.
  7. Retain artifacts tied to one source/constraint/tool/device configuration. Do not combine yesterday's tests with today's unverified bitstream into a release claim.

Task routing

Read only the relevant depth references; use their templates to retain reviewable decisions.

Task Reference Template
Establish device and external interface requirements Target and interface contracts Target contract
Review RTL semantics, inference and arithmetic RTL and arithmetic RTL contract
Build a self-checking verification strategy Simulation and verification Simulation plan
Review clocks, reset and domain crossings Clocks, reset and CDC CDC review
Diagnose timing or review constraints Timing and constraints Timing review
Decide pipelining, memory, DSP and implementation tradeoffs Implementation and resources RTL contract and timing review
Release an implementation or plan physical bring-up Release and hardware verification Implementation release

Read the full file on GitHub · 98 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. 1mo ago First seen · 98 lines · 97 tokens per session scan A 00694220016d

Subscribe to this mod's changes

fpga-development is a skill published in the GitHub repository magnus919/agent-skills (133 stars, last pushed 2d ago), licensed MIT. It adds 97 tokens to every session and 1,959 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-09-15.

Related

Other skills, from other repositories

running-openmed-ondevice

Run OpenMed models fully on-device with the MLX (Apple Silicon), CoreML (iOS/macOS), or ONNX/WebGPU (cross-platform/browser) backends, including convert-quantize-run workflows. Use when the user wants to deploy OpenMed at the edge, run NER/de-id on Apple Silicon, target iPhone/iPad/Mac, export to ONNX or WebGPU…

maziyarpanahi/openmed · 175 tokens

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…

synthetic-sciences/openscience · 73 tokens

actual-setup

Set up Actual Computer (actual.inc) inference in Hermes.

NousResearch/hermes-agent · 16 tokens

eightctl

Control Eight Sleep pods (status, temperature, alarms, schedules).

moltis-org/moltis · 16 tokens

klatch

Spawn genuinely independent parallel subagents — each assigned a distinct perspective role (Skeptic, Optimist, Pragmatist, Domain Expert, Contrarian) — to analyze a topic from independent viewpoints and synthesize divergent findings into a decision-ready roundtable output.

Snowflake-Labs/cocoplus · 54 tokens

cocoplus-config

CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.

Snowflake-Labs/cocoplus · 56 tokens