Borrowing it
Nothing to install: this file belongs to mitchdenny/hex1b. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mitchdenny/hex1b/main/.github/skills/widget-creator/SKILL.mdgit clone --depth 1 https://github.com/mitchdenny/hex1bWrote 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/mitchdenny/hex1b/widget-creator)<a href="https://agentmods.dev/skills/mitchdenny/hex1b/widget-creator"><img src="https://agentmods.dev/badge/skills/mitchdenny/hex1b/widget-creator/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/mitchdenny/hex1b/widget-creator"><img src="https://agentmods.dev/badge/skills/mitchdenny/hex1b/widget-creator.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.00046 | $0.07131 |
| Opus 5.5 | $0.00018 | $0.02852 |
| Sonnet 5.5 | $0.00009 | $0.01426 |
| Haiku 4.5 | $0.00005 | $0.00713 |
Grade A, and why
widget-creator 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.
How it starts
The opening of the file, as written. The whole thing — 958 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Widget Creator Skill
This skill provides a comprehensive step-by-step guide for AI coding agents to create new widgets in the Hex1b TUI library. Widgets are the building blocks of Hex1b applications, following a declarative pattern inspired by React.
Overview
Creating a widget in Hex1b involves several coordinated files:
| File | Purpose |
|---|---|
src/Hex1b/Widgets/{Name}Widget.cs |
Immutable widget record (describes what to render) |
src/Hex1b/Nodes/{Name}Node.cs |
Mutable node class (manages state, renders) |
src/Hex1b/{Name}Extensions.cs |
Fluent API extension methods |
src/Hex1b/Theming/{Name}Theme.cs |
Theme elements (colors, characters) |
tests/Hex1b.Tests/{Name}NodeTests.cs |
Unit tests |
Step-by-Step Process
Step 1: Define the Widget Record
Widgets are immutable record types that describe the desired UI. They capture configuration and event handlers but contain no rendering logic.
Location: src/Hex1b/Widgets/{Name}Widget.cs
Key principles:
- Use primary constructor parameters for required data
- Use
internalproperties withinitfor optional configuration - Event handlers use
Func<TEventArgs, Task>?pattern - Provide sync and async overloads for event handlers using
this with { }pattern - Implement
Reconcile()to create/update the corresponding node - Implement
GetExpectedNodeType()to return the node type
Template:
using Hex1b.Events;
using Hex1b.Nodes;
namespace Hex1b.Widgets;
/// <summary>
/// Brief description of what the widget does.
/// </summary>
/// <param name="PrimaryProperty">Description of the main property.</param>
public sealed record MyWidget(string PrimaryProperty) : Hex1bWidget
{
/// <summary>
/// ActionId for the activate action. Use "WidgetName.ActionName" naming
/// convention (PascalCase, omit "Widget" suffix from the widget name).
/// Define one static readonly ActionId per rebindable action.
/// </summary>
public static readonly ActionId Activate = new($"{nameof(MyWidget)}.{nameof(Activate)}");
/// <summary>
/// Optional configuration property.
/// </summary>
internal bool SomeOption { get; init; }
/// <summary>
/// Event handler for some action.
/// </summary>
internal Func<MyEventArgs, Task>? ActionHandler { get; init; }
/// <summary>
/// Sets a synchronous action handler.
/// </summary>
public MyWidget OnAction(Action<MyEventArgs> handler)
=> this with { ActionHandler = args => { handler(args); return Task.CompletedTask; } };
/// <summary>
/// Sets an asynchronous action handler.
/// </summary>
public MyWidget OnAction(Func<MyEventArgs, Task> handler)
=> this with { ActionHandler = handler };
internal override Hex1bNode Reconcile(Hex1bNode? existingNode, ReconcileContext context)
{
var node = existingNode as MyNode ?? new MyNode();
// Mark dirty if properties changed
if (node.PrimaryProperty != PrimaryProperty || node.SomeOption != SomeOption)
{
node.MarkDirty();
}
node.PrimaryProperty = PrimaryProperty;
node.SomeOption = SomeOption;
node.SourceWidget = this;
// Convert typed event handler to internal handler if needed
if (ActionHandler != null)
{
node.ActionCallback = async ctx =>
{
var args = new MyEventArgs(this, node, ctx);
await ActionHandler(args);
};
}
else
{
node.ActionCallback = null;
}
return node;
}
internal override Type GetExpectedNodeType() => typeof(MyNode);
}
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 · 958 lines · 46 tokens per session scan A 067b740e0368
widget-creator is a skill published in the GitHub repository mitchdenny/hex1b (181 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 7,131 once invoked, about $0.0002 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.
Other skills, from other repositories
react-ink
Use this skill when building terminal user interfaces with React Ink - interactive CLI apps, terminal dashboards, progress displays, or keyboard-driven TUI components. Triggers on React Ink, Ink components, terminal UI with React, useInput, useFocus, Box/Text layout, create-ink-app, and any task requiring rich…
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
mcp
Build or consume Model Context Protocol (MCP) servers and clients in .NET using the official MCP C# SDK, including stdio, Streamable HTTP, tools, prompts, resources, and capability negotiation. USE FOR: .NET MCP servers or clients; stdio versus HTTP transport choices; tools, resources, prompts, completions, and…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
semantic-kernel
Build AI-enabled .NET applications with Semantic Kernel using services, plugins, prompts, and function-calling patterns that remain testable and maintainable. USE FOR: adding AI-driven prompts, plugins, or orchestration to a .NET app; reviewing kernel construction, service registration, or plugin usage; building…
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…