worldforge: Skill for Codex

.codex/skills/tui-development/SKILL.md

tui-development is a skill for Codex from AbdelStark/worldforge. It costs 63 tokens per session (693 once invoked), scanned A, original, MIT.

A helper for developing the robotics showcase’s terminal user interface, or TUI—a text-based screen with panes and reports. It separates display code from robotics logic so the logic can be tested without the optional UI library.

In plain words
What is it for?
Use it to change robotics report panes, launch helpers, screenshots, visual tests, rendering, styles, and progress or error reporting.
Why use it?
It prevents UI changes from bringing back removed workflows or hiding failures, while keeping reports usable in tests, command-line output, screenshots, and documentation.

Skill for Codex

Written for Codex: agents/openai.yaml present.

This is AbdelStark/worldforge's own configuration. It tells Codex how to work on worldforge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything worldforge configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AbdelStark/worldforge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AbdelStark/worldforge/main/.codex/skills/tui-development/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/AbdelStark/worldforge

Made for: 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.

agentmods badge for tui-development

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/abdelstark/worldforge/tui-development"><img src="https://agentmods.dev/badge/skills/abdelstark/worldforge/tui-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 693 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00063 $0.00693
Opus 5.5 $0.00025 $0.00277
Sonnet 5.5 $0.00013 $0.00139
Haiku 4.5 $0.00006 $0.00069

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

Security

Grade A, and why

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

.codex/skills/tui-development/SKILL.md · 59 lines

How it starts

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

TUI Development

Architecture Boundary

  • src/worldforge/harness/robotics_launch.py: launcher and host-owned viewer helpers.
  • src/worldforge/harness/robotics_view.py: Textual-free robotics report model and constants.
  • src/worldforge/harness/robotics_tui_rendering.py: pure Rich renderable builders for panes.
  • src/worldforge/harness/tui.py: robotics-showcase-only Textual import surface.
  • src/worldforge/harness/tui_styles.py and tui_robotics_styles.py: Textual CSS constants.

Never import Textual from worldforge.__init__, worldforge.cli, or non-TUI harness modules.

Robotics TUI Engineering Contract

  • Treat the robotics showcase as a testable report renderer first and a Textual screen second.
  • Keep robotics summaries and screen state JSON-native so evidence can move between CLI, tests, screenshots, and docs.
  • Keep long-running optional runtime work behind explicit commands; UI state should report progress and failure without hiding the underlying exception context.
  • The removed world-creation/provider/eval/benchmark harness screens must not come back through this skill. Use CLI/docs surfaces for those workflows.

Workflow

  1. Read robotics_view.py, robotics_tui_rendering.py, robotics_launch.py, and tui.py before touching TUI modules.
  2. Keep all Textual imports inside harness/tui.py.
  3. Keep report rendering pure and deterministic outside Textual so tests can run without the harness extra.
  4. Update the relevant tests: test_robotics_tui_rendering.py, test_robotics_showcase.py, test_robotics_showcase_scripts.py, or focused harness report tests.
  5. Update screenshots only when UI behavior or documented visual state changed.
  6. Validate with focused robotics tests, optional-import boundary checks, and the --extra harness coverage gate when behavior changes.

Definition Of Done

  • Robotics report rendering works without the harness extra.
  • Changed robotics UI behavior is covered at the pure-rendering level before TUI-specific tests.
  • Textual imports remain isolated and optional-import boundary checks pass when imports moved.
  • Snapshot or screenshot updates are intentional and tied to verified behavior.

Read the full file on GitHub · 59 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.

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. 2mo ago First seen · 59 lines · 63 tokens per session scan A 7733ebf40a9d

Subscribe to this mod's changes

tui-development is a skill published in the GitHub repository AbdelStark/worldforge (108 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 693 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

sensing-track

Query flow event logs to answer questions about past sensing events — "Have you seen anybody between 10pm and midnight?", "Is there any motion in the last hour?", "What happened while I was away?". Also holds your OWN sleep history — "how many times have you slept?", "when do you usually go to sleep?".

autonomous-ai/autonomous-os · 70 tokens

sensing

React to passive device events tagged [sensing:...] — presence, sound, light, fire hazard — with inline emotion markers and optional short speech. Does NOT handle motion.activity (→ wellbeing) or emotion.detected / speechemotion.detected (→ user-emotion-detection).

autonomous-ai/autonomous-os · 60 tokens

environment

Interpret environmental sensor readings and sustained changes for room comfort and air quality. Use for [environment:initial] greeting context, [environment:update] events, questions about room temperature, humidity, measured CO2 or air quality, checking changes after ventilation or air cleaning, and room-feeling…

autonomous-ai/autonomous-os · 109 tokens

emotion

Express emotion through coordinated servo + LED + display eyes on EVERY conversational response. This is the PRIMARY response skill that makes the device feel alive. Do NOT use for ambiance lighting (use Scene) or custom LED colors (use LED Control).

autonomous-ai/autonomous-os · 49 tokens

guard

Guard mode for security monitoring. Two uses — (1) Toggle on/off when a friend says "guard mode", "watch the house", "I'm going out", or similar. (2) Handle any sensing event that carries a [guard-active] tag (e.g. [sensing:presence.enter][guard-active], [sensing:motion][guard-active]) with dramatic shock/curious…

autonomous-ai/autonomous-os · 101 tokens

led-control

Control the device's RGB light when the user asks for a SPECIFIC color (e.g. "yellow", "red", "yellow", "red", "turn on color X", "enable X light"), an LED effect, or turning LEDs off. Do NOT use for ambiance/activity lighting (use Scene) or emotion expression (use Emotion).

autonomous-ai/autonomous-os · 72 tokens