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/daxaur/openpaw/c-tasksnpx skills add daxaur/openpaw --skill c-tasksgit clone --depth 1 https://github.com/daxaur/openpawWrote 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/daxaur/openpaw/c-tasks)<a href="https://agentmods.dev/skills/daxaur/openpaw/c-tasks"><img src="https://agentmods.dev/badge/skills/daxaur/openpaw/c-tasks.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00530 |
| Opus 5 | $0.00025 | $0.00265 |
| Sonnet 5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
c-tasks 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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill supports three task managers. Detect which is available with which todoist-cli things-cli task and use accordingly.
Todoist — todoist-cli
todoist-cli list # List today's tasks
todoist-cli list --project "Work" # Tasks in a project
todoist-cli add "Task name" --due today --priority 2
todoist-cli add "Task" --project "Work" --label "urgent"
todoist-cli complete <task-id>
todoist-cli delete <task-id>
todoist-cli projects # List all projects
todoist-cli search "query"
Things 3 — things-cli
things-cli today # Today's tasks
things-cli list # All tasks
things-cli list --area "Work"
things-cli add "Task name" --when today --tag "urgent"
things-cli add "Task" --project "Project Name" --deadline "2026-03-01"
things-cli complete "Task name"
things-cli projects # List projects
things-cli areas # List areas
Taskwarrior — task
task list # List pending tasks
task next # Highest-priority next task
task add "Task name" due:tomorrow pri:H project:work
task add "Task" +tag1 +tag2
task <id> done # Complete a task
task <id> delete
task <id> modify priority:H
task project:work list # Filter by project
task +OVERDUE list # Overdue tasks
task summary # Project summary
Usage Guidelines
- Check which tool is installed before running commands.
- If multiple are installed, ask the user which they prefer or use the one matching their request context.
- For natural language dates, Todoist and Things handle them natively; Taskwarrior uses
due:YYYY-MM-DDordue:tomorrow.
Notes
- Todoist requires API token configured via
todoist-cli auth. - Things 3 requires macOS and the Things 3 app.
- Taskwarrior stores tasks locally in
~/.task/.
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.
- 5d ago First seen · 61 lines · 50 tokens per session scan A e61eef29a1ff
c-tasks is a skill published in the GitHub repository daxaur/openpaw (167 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 530 once invoked, about $0.0003 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
google-tasks-tool
Google Tasks integration for listing task lists and tasks and creating or updating tasks via OAuth2. Use when: fetching TODO lists, adding tasks, marking items complete, or switching task lists.
task-management
Manage Joel's task system in Todoist. Triggers on: 'add a task', 'create a todo', 'what's on my list', 'today's tasks', 'what do I need to do', 'remind me to', 'inbox', 'complete', 'mark done', 'weekly review', 'groom tasks', 'what's next', or when actionable items emerge from other work. Also triggers when Joel…
google_tasks_coordinator
Expert in managing project tasks via Google Tasks MCP. Handles creation, synchronization, and organization of tasks to maintain project momentum.
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
backfill-enumerate-drain
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline. Load this when handling a .added seed event with the planner on.
ai-meeting-notes
Messy notes → Clear action items. Instantly. Paste any meeting notes, transcript, or text. Get summaries, action items with owners and deadlines. Auto-saved, searchable, with integrated to-do tracking. No bot. No subscription. No setup.