Borrowing it
Nothing to install: this file belongs to KitionAI/kition. 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/KitionAI/kition/main/.codex/skills/kition-ui-development/SKILL.mdgit clone --depth 1 https://github.com/KitionAI/kitionWrote 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/kitionai/kition/kition-ui-development)<a href="https://agentmods.dev/skills/kitionai/kition/kition-ui-development"><img src="https://agentmods.dev/badge/skills/kitionai/kition/kition-ui-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.
<a href="https://agentmods.dev/skills/kitionai/kition/kition-ui-development"><img src="https://agentmods.dev/badge/skills/kitionai/kition/kition-ui-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00036 | $0.00857 |
| Opus 5.5 | $0.00014 | $0.00343 |
| Sonnet 5.5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
kition-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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kition UI Development
Use this skill for frontend changes in the Kition client repository.
Required first step
- Read
docs/kition-ui-development.mdbefore making structural or UI changes.
Rules
- Keep
src/appfor bootstrap, shell, routing, and global styles only. - Keep route redirects and path normalization in app-level routing, not inside page components.
- Put generic shared controls in
src/components. - Put business UI in
src/features/<domain>. - Put editor chrome, workspace tree, tabs, and shared editor navigation in
src/features/workspace. - Put AI chat, agent timeline, and agent-only helpers in
src/features/agent. - Put Agent session state, streaming lifecycle, and model-selection hooks in
src/features/agent. - Keep
Shell.tsxas route-level shell glue; do not move new Agent presentation logic or editor-page assembly back into it. - Treat Agent as a first-class domain alongside document, kits, and settings.
- Keep editor workspace pages on a stable chrome: topbar, sidebar, tab strip, editor pane.
- Keep workspace tree, media gallery, tab strip, topbar, and sidebar inside
src/features/workspace/components. - Keep workspace navigation helper types and workspace display logic inside
src/features/workspace/lib. - Keep workspace-local persistence helpers such as tabs, tree metadata, and sidebar width inside
src/features/workspace/lib. - Keep workspace tree shaping and folder-path helpers inside
src/features/workspace/lib. - Keep workspace tree state hooks and workspace tree action hooks inside
src/features/workspace/hooks. - Keep workspace topbar and item-menu action hooks inside
src/features/workspace/hooks. - Keep workspace editor-pane prop builders and panel-assembly hooks inside
src/features/workspace/hooks. - Keep workspace screen-level page composition inside
src/features/workspace/components, notsrc/app. - Keep workspace tab state and tab persistence hooks inside
src/features/workspace. - Never build a Markdown editor in Kition:
.mdfiles open in the Note kit's own editor inKitFrame(src/features/kits), and the agent changes notes withnote_run. - Move editor chrome presentation into workspace feature components instead of growing page-level JSX inline.
- Keep desktop settings subscription and synchronization hooks inside
src/features/settings/hooks. - Never build a table editor in Kition:
.ktablefiles open in the Table kit's own editor inKitFrame(src/features/kits), and Kition's own features reach tables throughsrc/api/kitTables.ts. - Use
Workspace*names for editor shell and navigation concerns. - Use
Kit*names for kit frames, kit editors, and their host. - Use
Agent*names for AI chat and agent execution flows. - Do not create or restore a
src/reactdirectory. - Do not introduce new catch-all UI folders like
data/when a domain folder already exists. - When a file grows past roughly 800 lines, split it instead of extending it inline.
- Prefer feature hooks or feature libs over new inline helper clusters inside
Shell.tsx. - Prefer a workspace hook for tab open/close/activate flows instead of rebuilding tab state inline in
Shell.tsx. - Prefer workspace hooks for tree loading, create/delete/move flows, and root switching instead of rebuilding worktree behavior inline in
Shell.tsx. - Prefer workspace hooks for topbar actions such as editor mode switching, import/export entrypoints, and item-menu commands instead of rebuilding them inline in
Shell.tsx. - Remove dead wrappers, dead pages, duplicated helpers, and stale imports during refactors.
- Take shared controls from Kition Tessera (
@kition/tessera-ui); add a missing generic control there, not app business logic.
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.
- 3d ago Changed 7777f131ac0a
- 4d ago Changed 6db477ea71e5
- 5d ago Changed · -4 lines 3ce251806695
- 6d ago Changed · -1 lines 712e4e927a80
- 11d ago Changed 55bbc962bd71
- 2mo ago First seen · 61 lines · 36 tokens per session scan A 878e7337fafb
kition-development is a skill published in the GitHub repository KitionAI/kition (549 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 857 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.
Other skills, from other repositories
agent-creator
Create custom AI subagents with proper plugin structure, persona generation, and companion routing skills.
agent-orchestration-improve-agent
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
agents-md
Create, revise, or audit AGENTS.md files from repository evidence, verified commands, and correctly scoped instructions without overwriting maintainer intent.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
access-review
Conduct periodic access reviews and certifications. Implement access governance and recertification workflows. Use when managing access compliance.
alerting-oncall
Set up alerting rules, configure on-call rotations, and manage incident response workflows.