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 adampoit/ai --skill taskwarriorgit clone --depth 1 https://github.com/adampoit/aiWrote 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/adampoit/ai/taskwarrior)<a href="https://agentmods.dev/skills/adampoit/ai/taskwarrior"><img src="https://agentmods.dev/badge/skills/adampoit/ai/taskwarrior/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/adampoit/ai/taskwarrior"><img src="https://agentmods.dev/badge/skills/adampoit/ai/taskwarrior.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.00050 | $0.00842 |
| Opus 5.5 | $0.00020 | $0.00337 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
taskwarrior 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskwarrior
Inspect and manage tasks with task.
task +PENDING export
List Tasks
Preferred command (JSON output):
task +PENDING export
With custom filters:
task project:work due:today +PENDING export
For tasks that fall between two dates (entry, completion, due, or modified time), use Bash variables:
start_date="<start-date>"
end_date="<end-date>"
task "((entry.after:${start_date} and entry.before:${end_date}) or (end.after:${start_date} and end.before:${end_date}) or (due.after:${start_date} and due.before:${end_date}) or (modified.after:${start_date} and modified.before:${end_date}))" export
Use task rc.verbose=nothing ... for concise text output when not using export.
Task Summary
Build summary counts with these commands:
task +PENDING export
task +OVERDUE export
task due:today +PENDING export
task due:tomorrow +PENDING export
task priority:H +PENDING export
Summarize counts plus notable tasks (for example overdue or high priority).
Task Details
Get one task by ID or UUID:
task <task-id-or-uuid> export
Add Task
Create a task (mutating):
task add "Write Q1 planning notes" project:planning due:tomorrow priority:M +work +writing
Attach Notes
task-note is an external Taskwarrior helper, not a built-in task command. Confirm it is installed before using it:
command -v task-note
It takes exactly one argument. It ensures the task has a Notes file: <notes-dir>/<uuid>.md (read this file for full content) annotation, then opens the note in an interactive editor via taskopen:
task-note <task-id-or-uuid>
Notes live in $XDG_DATA_HOME/tasknotes/<uuid>.md (default ~/.local/share/tasknotes/<uuid>.md).
Non-interactive (agents)
task-note <task> with no subcommand opens an editor, so agents should use the subcommands instead:
task-note <task-id-or-uuid> set <<'EOF'
# Note title
Note body...
EOF
task-note <task-id-or-uuid> append <<'EOF'
More details...
EOF
task-note <task-id-or-uuid> show # print the note contents
task-note <task-id-or-uuid> path # print the note file path
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 · 126 lines · 50 tokens per session scan A 8c33b9ab1084
taskwarrior is a skill published in the GitHub repository adampoit/ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 842 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".
openspec-archive-change
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
init-agent-sync
Initializes the AGENTSYNC.md hub for AI agent coordination and task tracking.
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.