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 KxSystems/kx-skills --skill kx-textinputgit clone --depth 1 https://github.com/KxSystems/kx-skillsWrote 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/kxsystems/kx-skills/kx-textinput)<a href="https://agentmods.dev/skills/kxsystems/kx-skills/kx-textinput"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-textinput/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/kxsystems/kx-skills/kx-textinput"><img src="https://agentmods.dev/badge/skills/kxsystems/kx-skills/kx-textinput.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 135 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00061 | $0.01716 |
| Opus 5 | $0.00030 | $0.00858 |
| Sonnet 5 | $0.00012 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
kx-textinput 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 9d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KX TextInput
Also read kx-dashboard-core for: envelope, screen/widget wrapper, data sources, ViewState, binding patterns, actions, notifications, and the pre-flight checklist.
key: "BasicComponents" · definitionId: "33" · ComponentName: "TextInput" · version: "v2.9.0"
A single-line (or multiline) text entry box. The typed value is published to a ViewState via Basics.Text and/or via Actions on Enter/focusout.
Other
BasicComponentsinput controls have their own dedicated skills — use those, not this one:
- kx-button — clickable action trigger (
definitionId: "25")- kx-datepicker — calendar date/time selector (
definitionId: "15")- kx-selectioncontrols — radio buttons / checkboxes (
definitionId: "34")
⚠️ Hazards — Read First
Basics.Textaccepts a ViewState binding — to publish user-typed text to a ViewState use{ "_dashboardsType": "viewstate", "value": "<vsName>" }, not a plain string.- Actions fire on Enter keypress AND focusout — use them to trigger data source re-execution or ViewState maps after the user types.
Type: "multiline"switches the input to a<textarea>— thefixedHeight/heightfields control its size.
Basics
{
"ComponentName": "TextInput",
"Name": "",
"Theme": "Dark",
"Text": { "_dashboardsType": "viewstate", "value": "<viewStateName>" },
"Type": "text",
"FontSize": 16,
"horizontal": "Center",
"vertical": "Middle",
"fixedWidth": false,
"width": 100,
"fixedHeight": false,
"height": 100
}
| Field | Values / Notes |
|---|---|
Text |
ViewState binding (to publish typed value) or plain string (to set a fixed initial value). Prefer the ViewState binding for interactive inputs. |
Type |
"text" (single line, default) | "search" (single line with clear ×) | "multiline" (textarea) |
fixedWidth |
true — use width (px); false — fills tile width |
fixedHeight |
true — use height (px); false — fills tile height (relevant for "multiline") |
FontSize |
Integer, default 16 |
horizontal |
"Left" | "Center" | "Right" |
vertical |
"Top" | "Middle" | "Bottom" |
Theme |
"Dark" | "Light" |
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.
- 9d ago First seen · 173 lines · 61 tokens per session scan A 23399733adaa
kx-textinput is a skill published in the GitHub repository KxSystems/kx-skills (16 stars, last pushed 6d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,716 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…