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 cloveric/tarocub --skill tarocub-service-opsgit clone --depth 1 https://github.com/cloveric/tarocubWrote 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/cloveric/tarocub/tarocub-service-ops)<a href="https://agentmods.dev/skills/cloveric/tarocub/tarocub-service-ops"><img src="https://agentmods.dev/badge/skills/cloveric/tarocub/tarocub-service-ops/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/cloveric/tarocub/tarocub-service-ops"><img src="https://agentmods.dev/badge/skills/cloveric/tarocub/tarocub-service-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00591 |
| Opus 5 | $0.00000 | $0.00296 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
tarocub-service-ops 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 11d 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.
What it actually says
TaroCub service ops (Lark fleet)
Manage the TaroCub Lark bot fleet through its own service manager. The commands take an absolute path (via ~), so they run from any directory.
Restart the fleet (most common)
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service restart --all
- Restarts every configured Lark instance. Idle bots restart immediately; the current instance (the one whose bot is running this command) auto-defers its own restart until its turn queue is idle — it can't kill itself mid-turn; a busy instance is skipped (not interrupted).
- Add
--forceto also restart busy instances — this interrupts their in-flight turn. Use it only when you mean to (the current instance is still deferred, never force-killed). - Do NOT hand-roll a per-instance restart loop (stopping/starting each bot by hand). Always use the manager command above.
Other service commands
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service status # status of the current instance
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service stop [--all] [--force]
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service start [--all]
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service logs # recent service logs
node ~/projects/cc-telegram-bridge/dist/src/index.js lark service doctor # diagnose config / connectivity
Notes
- A full TaroCub release ends with
restart --all(step 3 of the release ritual: commit → GitHub Release → restart & verify). This is that command. - The fleet is the configured Lark instances (e.g. ccfcc1/2/3, ccfgg1/2). One bot per instance, one instance per process; state lives under
~/.cctb/<instance>/. - If you only need to confirm a bot is alive,
lark service status(current instance) or checking the process is enough — don't restart unless asked.
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.
- 11d ago First seen · 35 lines · 0 tokens per session scan A 10837abac494
tarocub-service-ops is a skill published in the GitHub repository cloveric/tarocub (13 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 591 tokens. 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
node-backend
Node.js backend development patterns for Express, NestJS, Fastify, and Hono. Use when implementing APIs, authentication, middleware, services, and server-side logic with Node.js and TypeScript. Provides project structure, code patterns, and best practices.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
infer-completion-criteria
Infer measurable completion criteria for an agent-loop task from project docs, code, and AIWG standards when the user has not supplied --completion explicitly.
nl-router
Route natural language requests to appropriate skills and workflows by parsing intent and matching trigger patterns.