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 babyworm/rtl-agent-team --skill lint-tool-profilesgit clone --depth 1 https://github.com/babyworm/rtl-agent-teamWrote 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/babyworm/rtl-agent-team/lint-tool-profiles)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/lint-tool-profiles"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/lint-tool-profiles/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/babyworm/rtl-agent-team/lint-tool-profiles"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/lint-tool-profiles.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.00019 | $0.00464 |
| Opus 5 | $0.00010 | $0.00232 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
lint-tool-profiles 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 7d 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.
What it actually says
Lint Tool Profiles
Common Contract
- Prefer wrapper:
lint/scripts/run_lint.sh - All profiles must normalize output into:
errors,warnings,tool,log_path,replay_path
- Gate decision is based on normalized
errors == 0
Open-Source Baseline
verilator:lint/scripts/run_lint.sh --tool verilator -f rtl/filelist_top.f --outdir lint/lint
verible:lint/scripts/run_lint.sh --tool verible -f rtl/filelist_top.f --outdir lint/lint
slang:lint/scripts/run_lint.sh --tool slang -f rtl/filelist_top.f --outdir lint/lint- Auto-detects RTL vs TB based on source file paths:
- RTL (
rtl/): runs with-Weverythingfor maximum strictness — catchesalways_ffmulti-driver violations (VCS ICPD), uninitialized variables, width mismatches, etc. - TB (
sim/): runs with--allow-dup-initial-drivers— permitsinitial+always_ffon same signal (common testbench pattern)
- RTL (
- Only slang catches IEEE 1800 §9.2.2.4 multi-driver violations; Verilator and Verible do not
Commercial Profile
spyglass(binary:sg_shell, config key:sg_shell, script flag:--tool spyglass):lint/scripts/run_lint.sh --tool spyglass --top <top> -f rtl/filelist_top.f --outdir lint/lint- Note:
rat_config.jsonusessg_shellas tool key; runner scripts accept--tool spyglass
Severity Mapping
- Tool
error/fatal-> normalizederror - Tool
warning-> normalizedwarning - Unknown parse line -> keep raw log reference and mark parse caution
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.
- 7d ago First seen · 36 lines · 19 tokens per session scan A 311172300041
lint-tool-profiles is a skill published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 18d ago), licensed MIT. It adds 19 tokens to every session and 464 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
hardware-health-check
Out-of-band hardware health via Redfish BMC (read-only) — power state, component health, thermal and power readings, firmware inventory, SEL log triage. Use when determining whether a host is powered off versus unreachable, checking hardware faults, reviewing thermal or PSU state, or triaging BMC event logs.
boot-doctor-mcp
Deterministic PC no-boot / no-POST / no-display troubleshooting — real BIOS beep-code lookup and a ranked next-steps engine, no LLM guessing at hardware causes. Use this whenever the user describes a computer that won't turn on, won't POST, has no display output, is beeping, or asks for hardware troubleshooting steps…
fpga-hardware-design-and-review-guide
Comprehensive FPGA hardware design guide based on real-world project experience. Covers pipeline architecture, timing optimization, SystemVerilog coding patterns, CDC handling, and practical debugging techniques. Use this skill when: (1) designing FPGA modules with timing constraints, (2) implementing video processing…
vdebug
Trace failing signals through the RTL hierarchy, classify root cause, and write a debug report per issue — no fix is proposed.
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…