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 agentmods add skills/xuiltul/animaworks/chatwork-toolnpx skills add xuiltul/animaworks --skill chatwork-toolgit clone --depth 1 https://github.com/xuiltul/animaworksWhat 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 | $0.00047 | $0.00633 |
| Opus 5 | $0.00023 | $0.00316 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
chatwork-tool 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chatwork Tool
External tool for Chatwork messaging, search, and room management.
Invocation via Bash
Use Bash with animaworks-tool chatwork <subcommand> [args]. See Actions below for syntax.
Actions
send — Send message
{"tool_name": "chatwork", "action": "send", "args": {"room": "room name or ID", "message": "text"}}
messages — Get messages
{"tool_name": "chatwork", "action": "messages", "args": {"room": "room name or ID", "limit": 20}}
search — Search messages
{"tool_name": "chatwork", "action": "search", "args": {"keyword": "search term", "room": "room (optional)", "limit": 50}}
unreplied — Check unreplied messages
{"tool_name": "chatwork", "action": "unreplied", "args": {"include_toall": false}}
include_toall(optional, default: false): Include messages addressed to all
rooms — List rooms
{"tool_name": "chatwork", "action": "rooms", "args": {}}
mentions — Get mentions
{"tool_name": "chatwork", "action": "mentions", "args": {"include_toall": false}}
include_toall(optional, default: false): Include messages addressed to all
delete — Delete message (own messages only)
{"tool_name": "chatwork", "action": "delete", "args": {"room": "room name or ID", "message_id": "message ID"}}
sync — Sync messages (cache update)
{"tool_name": "chatwork", "action": "sync", "args": {"room": "room name or ID"}}
CLI Usage (S/C/D/G-mode)
animaworks-tool chatwork send ROOM MESSAGE
animaworks-tool chatwork messages ROOM [-n 20]
animaworks-tool chatwork search KEYWORD [-r ROOM] [-n 50]
animaworks-tool chatwork unreplied [--json]
animaworks-tool chatwork rooms
animaworks-tool chatwork mentions [--json]
animaworks-tool chatwork delete ROOM MESSAGE_ID
animaworks-tool chatwork sync [ROOM]
Notes
- Chatwork API Token must be configured in credentials
- Room can be specified by name or room ID
- Write token may be required for sending messages
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 First seen · 79 lines · 47 tokens per session scan A e3089a39f8b4
chatwork-tool is a skill published in the GitHub repository xuiltul/animaworks (254 stars, last pushed 3d ago), licensed Apache-2.0. It adds 47 tokens to every session and 633 once invoked, about $0.0002 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
inbox_check
Check aimail inbox status across AIPass branches.
email-triage
Classify incoming emails into triage categories using content analysis, sender profile memory, and thread detection. Produces a category (URGENT, REPLYNEEDED, FYI, NEWSLETTER, NOTIFICATION, SPAM) with confidence and reasoning.
Send emails directly from your agent. Supports HTML and plain text. Works with Unosend (5,000 free emails/month) or any SMTP provider.
slack-tools
Slack workspace management and automation specialist.
open-questions
Shows the user dashboard: pending questions the agent has logged for the user, goals with participants including user, and blocked goals grouped by blocker reason. Use whenever the user says "what do you need from me", "what's blocked", "what questions do you have", "what am I on the hook for", or invokes…
customer-email-assist
Review Gmail customer-support threads with a minimal-token, connector-first workflow. Use when Codex needs to read Gmail through the Codex Gmail connector, import cleaned messages into a local SQLite issue queue, apply deterministic cleanup and classification first, reserve model usage for JSON-only message…