What is coding_style?

Coding rules for Verilog-2001, a language used to describe synthesizable digital circuits. They cover file layout, module and signal names, and common reset and clock naming patterns.

Use them when writing or reviewing Verilog RTL, which is code intended to become hardware. They help structure modules, name signals, choose file extensions, and distinguish registered outputs and reset signals.

They make hardware code easier to read consistently and help avoid patterns that may not synthesize correctly. They also clarify how implementation and testbench files should be organized.

coding_style — Skill for Claude Code and Codex by ic-star-tech

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 ic-star-tech/ccfoundry-agent-kit --skill coding_style

Clone the repo

git clone --depth 1 https://github.com/ic-star-tech/ccfoundry-agent-kit

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ic-star-tech/ccfoundry-agent-kit/coding_style/github.svg)](https://agentmods.dev/skills/ic-star-tech/ccfoundry-agent-kit/coding_style)

Your own site

<a href="https://agentmods.dev/skills/ic-star-tech/ccfoundry-agent-kit/coding_style"><img src="https://agentmods.dev/badge/skills/ic-star-tech/ccfoundry-agent-kit/coding_style/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ic-star-tech/ccfoundry-agent-kit/coding_style"><img src="https://agentmods.dev/badge/skills/ic-star-tech/ccfoundry-agent-kit/coding_style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,223 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.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.01223
Opus 5.5	$0.00008	$0.00489
Sonnet 5.5	$0.00004	$0.00245
Haiku 4.5	$0.00002	$0.00122

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

Security

Grade A, and why

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

examples/verilog_module_writer/agent_space/skills/coding_style/SKILL.md · 157 lines

How it starts

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

Verilog Coding Style Guide

Trigger

Use this skill when writing or reviewing Verilog code to ensure consistency, readability, and synthesizability.

General Rules

File Organization

One module per file
Filename matches module name: rra.v contains module rra
Testbench files use _tb suffix: rra_tb.v
Use .v extension for Verilog-2001 (not .sv)

Module Declaration (Verilog-2001 ANSI style)

module module_name (
    input  wire        clk,
    input  wire        rst_n,     // active-low async reset
    input  wire [7:0]  data_in,
    output reg  [7:0]  data_out,
    output wire        valid
);

Naming Conventions

Element	Convention	Example
Modules	lowercase_snake	`round_robin_arbiter`
Signals	lowercase_snake	`data_valid`, `read_enable`
Parameters	UPPER_SNAKE	`DATA_WIDTH`, `ADDR_DEPTH`
Constants	UPPER_SNAKE	`IDLE`, `STATE_READ`
Active-low signals	`_n` suffix	`rst_n`, `cs_n`, `wr_n`
Clock signals	`clk` prefix	`clk`, `clk_div2`
Reset signals	`rst` prefix	`rst_n`, `rst_sync`
Registered outputs	`_reg` suffix (internal)	`count_reg`, `state_reg`
Next-state signals	`_next` suffix	`state_next`, `count_next`

Reset Strategy

Always use async active-low reset (negedge rst_n)
Reset all registers to known values
Use consistent reset pattern:

always @(posedge clk or negedge rst_n) begin
    if (!rst_n) begin
        state <= IDLE;
        count <= 0;
    end else begin
        state <= state_next;
        count <= count_next;
    end
end

Combinational Logic

Use always @(*) for combinational blocks
Assign all outputs in every branch to avoid latches
Use blocking assignments (=) in combinational blocks
Use non-blocking assignments (<=) in sequential blocks

// GOOD: Combinational with always @(*)
always @(*) begin
    grant = 4'b0000;  // default
    case (state)
        IDLE:    grant = 4'b0000;
        GRANT_0: grant = 4'b0001;
        GRANT_1: grant = 4'b0010;
        default: grant = 4'b0000;
    endcase
end

Read the full file on GitHub · 157 lines

Files

What ships with it

1 file 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.

skill_meta.json 312 B

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.

2mo ago First seen · 157 lines · 19 tokens per session scan A de9f38fe2c0a

Subscribe to this mod's changes

coding_style is a skill published in the GitHub repository ic-star-tech/ccfoundry-agent-kit (24 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,223 once invoked, about $0.0001 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.

Hardware and IoT

coding_style next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
coding_styleic-star-tech/ccfoundry-agent-kit	Skill	24	5mo ago	MIT	A	19	Claude Code, Codex
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
jetson-diagnosticNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code, Codex
holoscan-install-wheelNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	34	Claude Code, Codex
offensive-z-waveSnailSploit/Claude-Red	Skill	10k	25d ago	MIT	A	113	Claude Code, Codex
doca-socket-relayNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	236	Claude Code, Codex
hsb-flashNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	B	94	Claude Code