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 Gonglitian/agent-skills --skill ghostty-cjk-input-debuggit clone --depth 1 https://github.com/Gonglitian/agent-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/gonglitian/agent-skills/ghostty-cjk-input-debug)<a href="https://agentmods.dev/skills/gonglitian/agent-skills/ghostty-cjk-input-debug"><img src="https://agentmods.dev/badge/skills/gonglitian/agent-skills/ghostty-cjk-input-debug/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/gonglitian/agent-skills/ghostty-cjk-input-debug"><img src="https://agentmods.dev/badge/skills/gonglitian/agent-skills/ghostty-cjk-input-debug.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.00291 | $0.04246 |
| Opus 5 | $0.00146 | $0.02123 |
| Sonnet 5 | $0.00058 | $0.00849 |
| Haiku 4.5 | $0.00029 | $0.00425 |
Grade B, and why
ghostty-cjk-input-debug scanned grade B with 1 finding 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get install -y fcitx5 fcitx5-chinese-addons \ The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 284 lines · 291 tokens per session scan B 4da038b7b079
ghostty-cjk-input-debug is a skill published in the GitHub repository Gonglitian/agent-skills (2 stars, last pushed 2mo ago), with no licence file. It adds 291 tokens to every session and 4,246 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
js-regex-cjk-word-boundary
Fix JavaScript regex failures when matching CJK (Chinese/Japanese/Korean) text using \b word boundaries. Use when: (1) Regex pattern with \b silently fails to match Japanese, Chinese, or Korean text, (2) Pattern works for Latin/ASCII text but not CJK, (3) hasDriverLicenceCue or similar text-detection function returns…
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
Network diagnostics
Localize connectivity failures across DNS, routing, NSGs, firewalls, private endpoints, transport, TLS, and application response.
fec-debug-framework
A step-by-step method for finding the cause of front-end build failures, browser errors, broken screens, failed requests, or incorrect data. It separates build, runtime, visual, and API problems and uses evidence to test possible causes.
fec-legacy-to-modern-migration
A guide for moving older front-end code—such as JavaScript, jQuery, HTML/CSS, server-rendered pages, or old frameworks—to newer tools while keeping the same behavior. It covers gradual migrations as well as modernising parts of a multi-page site.
hardening-resilience
Evaluate error handling, i18n, text overflow, and edge cases.