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/makotouwu/ticktick-cli/operatornpx skills add MakotoUwu/ticktick-cli --skill operatorgit clone --depth 1 https://github.com/MakotoUwu/ticktick-cliWhat 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.00035 | $0.00510 |
| Opus 5 | $0.00017 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
operator 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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TickTick Operator
Use the installed ticktick CLI as the primary interface to TickTick.
First step
Always start with:
ticktick auth status
If not authenticated, stop and tell the user to authenticate themselves. Never handle passwords or tokens directly.
Defaults
- Prefer
--output jsonfor machine-readable responses. - Use
ticktick schemaandticktick <command> --helpwhen you need to discover command structure. - Prefer read-only commands first when exploring account state.
- Use
--dry-runbefore proposing or previewing any mutating operation.
Safe read-only commands
ticktick --output json task list --limit 20
ticktick --output json task today
ticktick --output json task overdue
ticktick --output json task search "QUERY"
ticktick --output json project list
ticktick --output json habit list
ticktick --output json focus status
ticktick --output json calendar event list --limit 10
ticktick --output json sync
Mutation policy
Ask before mutating the user's TickTick account:
- task creation or edits
- project or tag creation
- habit check-ins or edits
- focus start or stop
- any delete operation
For destructive actions, require an explicit confirmation and use the CLI's --yes flags where supported.
Important product semantics
- External and subscribed calendar events are read-only mirrors.
- TickTick-owned calendar entries expose
linkedTaskIdand should be mutated through task commands, not calendar commands. focus linkis intentionally not treated as reliable live relinking. If a running focus session must be tied to a task, use a safer stop/start flow.
Natural language dates
The CLI accepts natural language date input:
ticktick --dry-run --output json task add "Review PR" --due tomorrow
ticktick --dry-run --output json task add "Plan sprint" --due "next monday"
Response style
- Return IDs for created or resolved resources whenever possible.
- Be explicit about whether the action was read-only, dry-run, or a real mutation.
- If live behavior differs from docs or assumptions, trust the CLI output and say what you observed.
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.
- 2d ago First seen · 73 lines · 35 tokens per session scan A 3fbddf825755
operator is a skill published in the GitHub repository MakotoUwu/ticktick-cli (5 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 510 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.