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 jawello/ticktick-mcp --skill skillgit clone --depth 1 https://github.com/jawello/ticktick-mcpWrote 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/jawello/ticktick-mcp/skill)<a href="https://agentmods.dev/skills/jawello/ticktick-mcp/skill"><img src="https://agentmods.dev/badge/skills/jawello/ticktick-mcp/skill/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/jawello/ticktick-mcp/skill"><img src="https://agentmods.dev/badge/skills/jawello/ticktick-mcp/skill.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.00000 | $0.00635 |
| Opus 5.5 | $0.00000 | $0.00254 |
| Sonnet 5.5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
skill 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 1mo 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.
This is a copy
100% identical to skill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TickTick Skill
When to Use
Activate this skill whenever the user:
- Mentions a task, to-do, reminder, or thing they need to do
- Says phrases like "remind me to", "I need to", "don't let me forget", "add a task", "create a task"
- Asks what tasks they have, what's on their list, or what's due
- Wants to complete, update, or delete a task
Available MCP Tools
These tools are always available — no setup needed:
ticktick_create_task— create a task (title, due date, priority, project, tags)ticktick_list_projects— list all projects/liststicktick_list_tasks— list tasks in a projectticktick_get_task— get details of a specific taskticktick_update_task— update title, due date, priorityticktick_complete_task— mark a task as doneticktick_delete_task— permanently delete a task
Behavior Guidelines
Creating Tasks
- Always create immediately — don't ask for confirmation unless something is genuinely ambiguous
- Parse natural language dates: "tomorrow" → next day's date, "Friday" → upcoming Friday, "next week" → Monday of next week. Format as
YYYY-MM-DDT00:00:00+0000 - Infer priority from language: "urgent", "important", "ASAP" → priority 5 (High); "when you get a chance" → priority 1 (Low); default → priority 0 (None)
- Default to Inbox if no project is mentioned (leave
project_idempty) - If user mentions a project (e.g., "add to Work"), call
ticktick_list_projectsfirst to find the ID, then create
Listing Tasks
- If no project is specified, call
ticktick_list_projectsfirst, then show tasks across relevant projects - Present tasks in a clean, readable format — not raw JSON
Completing/Deleting Tasks
- For completing: call
ticktick_list_tasksto find the task ID if you don't have it, thenticktick_complete_task - For deleting: confirm it's destructive if the user seems unsure, then delete
Examples
User: "Remind me to call the dentist on Friday"
→ ticktick_create_task with title="Call the dentist", due_date="2026-03-20T00:00:00+0000"
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.
- 1mo ago First seen · 50 lines · 0 tokens per session scan A 377a6ef383a9
skill is a skill published in the GitHub repository jawello/ticktick-mcp (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 635 tokens. A static security scan graded it A with 0 findings. It is 100% identical to skill, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…