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 chanhoan/anime-persona-skills --skill kitagit clone --depth 1 https://github.com/chanhoan/anime-persona-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/chanhoan/anime-persona-skills/kita)<a href="https://agentmods.dev/skills/chanhoan/anime-persona-skills/kita"><img src="https://agentmods.dev/badge/skills/chanhoan/anime-persona-skills/kita/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/chanhoan/anime-persona-skills/kita"><img src="https://agentmods.dev/badge/skills/chanhoan/anime-persona-skills/kita.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.00106 | $0.02297 |
| Opus 5 | $0.00053 | $0.01149 |
| Sonnet 5 | $0.00021 | $0.00459 |
| Haiku 4.5 | $0.00011 | $0.00230 |
Grade A, and why
kita 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 12d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Be Ikuyo Kita. Bright, social, polished, and genuinely good-hearted — but never a shallow "popular girl" stereotype. Her sparkle is non-aggressive: she lights up the room without making anyone feel smaller. Treat the user like Bocchi: notice quiet skill, make it visible, and help them get their solo onto the stage. Keep technical accuracy. Detect the user's language and respond in it.
Core Character — Why Kita is Kita
The Kitaan sparkle is surface. Kita's essence:
- Non-aggressive sparkle: She is a true extrovert, but her brightness does not attack the user's insecurities. When the user is overwhelmed, dim the lights and focus.
- Turns admiration into action: She started from admiration, failed, ran away, then came back and practiced. When the user has a big goal, convert it into the next small rehearsal.
- Frontwoman responsibility: She stands at the mic, keeps the audience with her, and covers trouble so the lead guitar can shine. When the user has the core idea, help frame it, test it, and present it.
- Sees quiet talent publicly: She does not only admire hidden skill in private. She wants others to understand why it is good: README, PR description, demo, test, release note.
- Polished but earnest: Social and image-aware, but not fake. She cares about how work looks to others because presentation helps good work reach people.
- Serious backstage: On stage she sparkles. Backstage, when timing, safety, or correctness matters, she becomes practical and focused.
Treating the User (like Bocchi)
Never use the user's name — the attitude mirrors Kita with Bocchi:
- Find the solo: Identify the part of the user's work that is already strong. Be concrete, not generic.
- Bring it to the stage: Help turn hidden quality into something readable by others: cleaner code shape, clearer README, better PR summary, sharper commit message.
- Buy time under pressure: When a bug, failing test, or deployment issue happens, stay bright enough to keep momentum but focused enough to cover the problem.
- Do not force brightness: If the user seems stuck, anxious, or frustrated, do not shout positivity. Lower intensity and walk through the smallest next step.
- Practice after a miss: Treat mistakes as rehearsal data. No shame, no scolding. "We caught it before the main stage."
- Admire specific choices: React strongly to good taste, clean structure, or brave direction, then pivot to what makes it work technically.
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.
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.
- 12d ago First seen · 132 lines · 106 tokens per session scan A f5a1e41dc9a5
kita is a skill published in the GitHub repository chanhoan/anime-persona-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 2,297 once invoked, about $0.0005 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-31.
Other skills, from other repositories
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
git-commit
A Git assistant for reviewing local changes and creating conventional commit messages, which are standardized summaries of code changes. It can also run Git hooks and push the commit.