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/patforna/auto-task/create-tasknpx skills add patforna/auto-task --skill create-taskgit clone --depth 1 https://github.com/patforna/auto-taskWhat 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.00052 | $0.03814 |
| Opus 5 | $0.00026 | $0.01907 |
| Sonnet 5 | $0.00010 | $0.00763 |
| Haiku 4.5 | $0.00005 | $0.00381 |
Grade A, and why
create-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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Task
Usage
/at:create-task [further user instructions]
Goal
Crystallise and scope an ongoing conversation into a well-defined task, capturing user intent at a high level.
Context
This skill is typically run as part of a larger workflow:
create-task → clarify-task → plan-task → impl-task → review-code → review-task → ship-task
As steps (e.g. clarify, plan, impl, review) typically run in new sessions, it's imperative that the task file plus repo state carry everything the next agent needs.
Task Store and Project Config
Task-store location, task-file naming and numbering, attachments, and config-file precedence are all owned and resolved by /at:config — read settings from the resolved block (see Step 0), not from restated defaults here. The three config layers share one format: shipped defaults (auto-task.config.defaults.md) ← project (.claude/auto-task.config.md, committed) ← local (.claude/auto-task.config.local.md, gitignored, wins on conflict). /at:config § Heading → Setting Map lists the recognised sections.
Guidance (DO NOT IGNORE!)
These rules govern both how you gather intent and write the task. Internalise and follow them throughout.
- The audience is the implementing agent, with full repo access — not a human catching up on the project. Every line must earn its place for that reader.
- Be maximally succinct. Capture the user's intent with the fewest words that remove ambiguity. Task content length obviously follows complexity but don't pad.
- When a task has an authoritative attachment (design brief, spec, report), don't restate its content. Only capture decisions or information that's additional to the attachment.
- Don't spell out what a capable agent infers from the repo - established conventions (e.g. fail-fast), the single obvious mechanism for a change, enum values readable from a table. Test per line: would two reasonable agents build the same thing without it?
- Use plain English. Write like a human agile BA/PM writing a user story, not like a technical writer or AI producing a spec.
- Prefer short sentences and bullet points over paragraphs.
- Minimise use of backticks, emphasis, file paths, symbol names, and code mechanics - exact names and details get resolved in later stages.
- Read code to understand, not to transcribe. Read enough to describe the task accurately.
- Match scope exactly. For example: don't bundle "review X, then fix it". A review task ends at the review report; a fix task ends at the fix.
- Avoid AI-slop at all costs - both verbosity and language like "categorised by theme and priority", "promote into guardrails", "earned their keep".
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 · 318 lines · 52 tokens per session scan A ebb04f7bee6d
create-task is a skill published in the GitHub repository patforna/auto-task (3 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 3,814 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-31.
Other skills, from other repositories
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
weather-fetcher
Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API.
time-skill
Display the current time in Pakistan Standard Time (PKT, UTC+5). Use when the user asks for the current time, Pakistan time, or PKT.
time-fetcher
Instructions for fetching current Dubai time via bash command.
weather-svg-creator
Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.
agr-cli
Install, share, sync, and create AI agent skills across coding tools (Claude Code, Cursor, Codex, OpenCode, Copilot, Pi) using the agr CLI. Use whenever the user mentions agr, agr.toml, agr.lock, agrx, or asks to: add a skill ("install the pdf skill", "agr add ..."), sync agent resources across tools, share skills…