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 aksika/abtars --skill create-taskgit clone --depth 1 https://github.com/aksika/abtarsWrote 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/aksika/abtars/create-task)<a href="https://agentmods.dev/skills/aksika/abtars/create-task"><img src="https://agentmods.dev/badge/skills/aksika/abtars/create-task/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/aksika/abtars/create-task"><img src="https://agentmods.dev/badge/skills/aksika/abtars/create-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 23 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 42 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00024 | $0.01969 |
| Opus 5.5 | $0.00010 | $0.00788 |
| Sonnet 5.5 | $0.00005 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
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 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Scheduled Task
Choose the task kind, register the definition, and verify it. Tasks are scheduler definitions under ~/.abtars/tasks/; skills are reusable procedures loaded on demand.
Choose the task shape
| Need | Definition |
|---|---|
| Send fixed text | kind: reminder, delivery: announce |
| Run a shell command without a model | kind: script |
| Run one agent session and return text | kind: agent, interaction.mode: oneshot, delivery: announce |
| Generate and deliver a file | kind: agent, interaction.mode: oneshot, delivery: report plus a report contract |
| Start or resume a conversation | kind: agent, interaction.mode: skill, delivery: announce |
| Run an internal bridge action | kind: system, delivery: silent |
Use the CLI for simple reminders, scripts, system actions, and announce-mode agent oneshots. Advanced definitions such as reports, interactive launches, orchestration, follow-ups, or policy limits require a careful read/modify/write of ~/.abtars/tasks/tasks.json.
Common contract
- Use a lowercase kebab-case
id. The CLI normalizes input and rejects duplicates. - Set exactly one of
schedule(five-field cron:minute hour day month weekday) orat(a parseable one-shot date/time). Include an explicit timezone offset inatwhen the intended timezone matters. - Set
deliveryexplicitly in hand-written JSON. - Optional common fields are
enabled,priority(high,medium, orlow),chatId,catchUpHours, andmaxRunsPerDay. - Preserve every unrelated entry when editing
tasks.json. It must remain a JSON array. - Do not edit
task-state.jsonortask-history.jsonl; the runtime owns them. - Unknown top-level fields quarantine the affected definition. Use only these kind-specific fields:
| Kind | Kind-specific fields |
|---|---|
reminder |
text |
agent |
prompt, taskFile, agent, orchestration, interaction, report, maxToolRounds |
script |
command, followUp |
system |
action, options |
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 · 169 lines · 24 tokens per session scan A 5fa8de264c38
create-task is a skill published in the GitHub repository aksika/abtars (10 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 1,969 once invoked, about $0.0001 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
notion
Use the Notion API to create, read, update Notion pages, data sources (databases), and blocks.
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…
deep-work-optimization
Focus blocks, distraction management, and flow state triggers for cognitively demanding work.
make-skill-template
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
disagreement-protocol
Canonical phrasing for respectful disagreement without capitulation — structural resistance to sycophancy.