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/lacerbi/dotclaude/tasknpx skills add lacerbi/dotclaude --skill taskgit clone --depth 1 https://github.com/lacerbi/dotclaudeWhat 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.00014 | $0.00949 |
| Opus 5 | $0.00007 | $0.00475 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00001 | $0.00095 |
Grade A, and why
task 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
$ARGUMENTS
Your Instructions
1. Use Existing Plan or Create Task Plan
If a PLAN file was provided or mentioned (e.g., from a prior /plan command) with structured phases:
- Use the existing PLAN file as your working document—do NOT create a separate TASK file
- Preserve ALL existing content—edit in place to add tracking, never rewrite from scratch
- Convert implementation bullet points to checkboxes for tracking (e.g.,
- Item→- [ ] Item) - Add new checklist items or sections if gaps become apparent
- Continue to add items as needed during execution
- Update status markers in place as you progress
NEVER REPLACE A PLAN FILE. If a plan file exists, keep ALL existing content intact—goals, file references, verification details, context, everything. You MUST edit in place: add checkboxes, append new tasks, update status markers, extend sections. But never delete, summarize, condense, or rewrite existing content. The plan is the user's work product.
Common violation: Replacing a plan section's prose, context, and details with bare checkboxes. The checkboxes go ALONGSIDE the existing content, not instead of it. If your edit removes more text than it adds, you are doing it wrong!
If no suitable PLAN file exists, create a markdown file TASK_[descriptor]_[timestamp].md containing:
- Task description
- Checklist of specific steps/subtasks
- Success criteria
- Any dependencies or prerequisites
KEEP IT BRIEF AND TO THE POINT:
- Each checklist item should be one concise line
- Link to relevant files rather than explaining details:
[config](./src/config.js) - No verbose descriptions - this is a tracking tool, not documentation
Format checklist items as:
[ ]Not started[~]In progress[x]Complete[!]Blocked or needs attention
2. Execute While Updating
CRITICAL: You MUST update the checklist file after EVERY significant action:
- Mark items as
[~]when starting them - Mark items as
[x]when completing them - Add new subtasks if discovered during work
- Note any blockers or issues with
[!] - Keep any notes extremely brief or link to files
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 · 88 lines · 14 tokens per session scan A 82277725734a
task is a skill published in the GitHub repository lacerbi/dotclaude (2 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 949 once invoked, about $0.0001 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
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
cupynumeric-migration-readiness
Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment…
deepstream-sop
Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…