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/babyworm/rtl-agent-teamnpx agentmods add skills/babyworm/rtl-agent-team/cdc-tool-profilesWrote 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/cdc-tool-profiles)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/cdc-tool-profiles"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/cdc-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/cdc-tool-profiles"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/cdc-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.00020 | $0.01377 |
| Opus 5 | $0.00010 | $0.00688 |
| Sonnet 5 | $0.00004 | $0.00275 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
cdc-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 5d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CDC & Structural Analysis Tool Profiles
Quantitative + Qualitative Gate Philosophy
svlens provides quantitative measurements (scores, violation counts, complexity metrics) to add consistency to the LLM's qualitative judgment. Phase gate decisions require BOTH:
- Quantitative: svlens tool reports (JSON) — violation counts, health scores, complexity metrics
- Qualitative: LLM assessment of design intent, context, and risk
Neither alone is sufficient. A zero-violation svlens report does not auto-pass a gate if the LLM identifies architectural concerns. Conversely, the LLM cannot override quantitative violations without documented justification (waiver with rationale).
When commercial tools are available, they serve as the signoff authority. svlens provides supplementary crosscheck data — useful for early-stage CI, pre-signoff screening, and adding quantitative rigor to LLM-driven reviews.
Common Contract
- Prefer wrapper:
lint/scripts/run_cdc.sh - Output classes:
VIOLATIONCAUTIONCONVENTIONINFOWAIVED
- Gate fail when unwaived
VIOLATIONexists.
Open-Source Baseline: svlens (https://github.com/babyworm/svlens)
svlens is a unified structural analysis toolkit with three modes sharing one elaboration:
svlens cdc — Clock Domain Crossing Analysis
lint/scripts/run_cdc.sh --tool structural --top <top> -f rtl/filelist_top.f --outdir lint/cdc(structural mode auto-runs svlens crosscheck when installed)lint/scripts/run_cdc.sh --tool svlens --top <top> -f rtl/filelist_top.f --outdir lint/cdc(standalone mode)- 8 synchronizer patterns (2-FF, 3-FF, gray, handshake, async FIFO, MUX, pulse, Johnson)
- Quality checks: reconvergence, glitch path, fan-out-before-sync, reset sync, non-2^N FIFO
- Outputs: md + json + sdc + waiver yaml
- Key JSON fields:
summary.violations,summary.cautions, per-crossingseverity+sync_type
svlens conn — Port Connectivity Analysis
svlens conn --format all --top <top> -f rtl/filelist_top.f -o sim/conn/reports- Width mismatch, type mismatch, dangling output, undriven input detection
- Protocol completeness (
--check-protocol), naming convention (--check-convention) - Expected connectivity validation (
--expect connectivity_spec.yaml) - Key JSON fields:
analysis.overall_score,analysis.module_health,summary.errors
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.
- 5d ago First seen · 109 lines · 20 tokens per session scan A 6152628bb6dd
cdc-tool-profiles is a skill published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 16d ago), licensed MIT. It adds 20 tokens to every session and 1,377 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
qa-review
QA review for code changes — test coverage analysis, edge case identification, test plan generation, regression detection, test health tracking over time.
readable-verilog-generator
Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed…
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
fresh-eyes-loop
A repeatable quality-review process using two independent agents: one reviews and verifies, while the other fixes issues. P0 and P1 mean the highest-severity problem levels.
rtl-review
Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.
kicad-pcb-review
Use this skill when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.