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/confignpx skills add patforna/auto-task --skill configgit 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.00054 | $0.02445 |
| Opus 5 | $0.00027 | $0.01222 |
| Sonnet 5 | $0.00011 | $0.00489 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
config 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config
Usage
/at:config — inspect the resolved settings for the current repo, with each value's origin (see § Inspect).
Setting-consuming skills don't call this as a command. They follow § Resolve — via their mandatory Step 0 — to obtain a resolved block, then read settings.* from it. Every setting's canonical default lives in the shipped defaults file (§ Resolve layer 1) and nowhere else, so a skill never restates a default: change it there and every consumer follows.
Scope This Slice
This slice populates only the settings /at:create-task consumes: settings.task_store.* and settings.feedback_snapshots.* — their defaults live in the shipped auto-task.config.defaults.md (§ Resolve layer 1). Both are static (no environment detection), so § Detection is an empty stub for now.
The other settings still live inline in their own skills and migrate in later slices. Their config-file headings are already recognised here (see § Heading → Setting Map) so an existing full config raises no false warnings during migration — they just don't resolve to live settings yet.
Settings
The settings /at:config owns this slice. Their default values live in the shipped auto-task.config.defaults.md (§ Resolve layer 1), not here — this section maps each setting to its meaning and its override label.
| Setting | Meaning | Resolved by | Override (heading → label) |
|---|---|---|---|
settings.task_store.location |
where task files live | static | ## Task Store → location: |
settings.task_store.create |
how a new task file is created | static | ## Task Store → create: |
settings.task_store.status |
how a task's status changes | static | ## Task Store → status: |
settings.feedback_snapshots.dir |
out-of-repo dir for post-clarify snapshots | static | ## Feedback Snapshots → dir: |
settings.feedback_snapshots.exemplar |
calibration exemplar read before writing a task | static | ## Feedback Snapshots → exemplar: |
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 · 131 lines · 54 tokens per session scan A 14cc59de1f69
config is a skill published in the GitHub repository patforna/auto-task (3 stars, last pushed 14d ago), licensed MIT. It adds 54 tokens to every session and 2,445 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
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…
agr-release
Release process for the agr package. Handles version bumping (major/minor/patch/beta), changelog updates, pre-release quality checks, git tagging, and monitoring the GitHub Actions publish pipeline. Use this skill whenever the user wants to cut a release, bump the version, publish to PyPI, or asks about the release…
release
Cut a paad release — pick the semver bump from what is in [Unreleased], run make release, merge, tag, and verify the published plugin.