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 davekilleen/Dex --skill todoist-setupgit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/todoist-setup)<a href="https://agentmods.dev/skills/davekilleen/dex/todoist-setup"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/todoist-setup/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/davekilleen/dex/todoist-setup"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/todoist-setup.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.00076 | $0.02111 |
| Opus 5.5 | $0.00030 | $0.00844 |
| Sonnet 5.5 | $0.00015 | $0.00422 |
| Haiku 4.5 | $0.00008 | $0.00211 |
Grade A, and why
todoist-setup 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.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Todoist Setup
Connect your Todoist account so Dex can work with your Todoist tasks whenever you ask — check what's due, create a task there instead of in Dex, or mark something done.
What this enables (on request): Once connected, say "sync with Todoist" — Dex pushes new tasks to the right Todoist project, marks completions, and pulls back tasks you completed or created in Todoist directly. Sync runs on demand; Dex does not poll Todoist in the background without you asking.
What This Enables
Once connected, you can ask Dex to:
- See what's due: "What's due in Todoist today?" — including alongside your daily plan
- Create there instead: "Add that to Todoist, not Dex" during triage or any conversation
- Complete from chat: "Mark the invoice task done in Todoist"
- Cross-check: "Anything in Todoist that isn't tracked in Dex?"
Privacy
- Dex reads and writes your Todoist tasks only when you ask it to
- Your API key stays local in the ignored vault-root
.envfile. Tracked YAML stores only its variable name. - Dex never shares your Todoist data with third parties
When to Run
- User types
/todoist-setup - User asks about connecting Todoist or task sync
- User wants Todoist tasks in daily plans
- During
/integrate-mcpif Todoist is mentioned
Setup Flow
Step 1: Check if Already Connected
- Check
System/integrations/config.yamlfor atodoist:section withenabled: truethroughcore.utils.strict_yaml.load_yaml_path; refuse duplicate keys, aliases, anchors, or merge mappings before reading or writing any setup field. - If enabled, test authentication with the read-only health check
- If healthy, skip to Reconfiguration section below
- If not configured or unhealthy, continue to Step 2
Step 2: Explain What We're Setting Up
Say:
**Let's connect Todoist to Dex.**
Once connected, you can ask me to check, create, or complete Todoist tasks
right from our conversations.
**What you'll need:**
- Your Todoist API token (I'll show you where to find it)
- About 2 minutes
**Ready to go?**
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 · 255 lines · 76 tokens per session scan A f7c1d4abde52
todoist-setup is a skill published in the GitHub repository davekilleen/Dex (508 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 2,111 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…