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/zexion7873/copilot-setting/tasksnpx skills add zexion7873/copilot-setting --skill tasksgit clone --depth 1 https://github.com/zexion7873/copilot-settingWrote 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/zexion7873/copilot-setting/tasks)<a href="https://agentmods.dev/skills/zexion7873/copilot-setting/tasks"><img src="https://agentmods.dev/badge/skills/zexion7873/copilot-setting/tasks.svg" alt="Measured on agentmods" 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 | $0.00076 | $0.00761 |
| Opus 5 | $0.00038 | $0.00380 |
| Sonnet 5 | $0.00015 | $0.00152 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
tasks 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tasks — Workflow
Atomic task decomposition from an approved plan.
Phase 1 — Parse Source
Locate the approved plan at docs/plans/<feature>/plan.md (the plan skill writes there, one folder per feature/change). If the user named a feature, read that folder's plan.md. If exactly one plan folder exists, use it. If none exists or the source is ambiguous, stop and ask — do not invent a task list from scratch; redirect to the plan skill when no plan exists yet.
From the plan, extract: phases/goals, file list, dependencies, constraints, and Acceptance Criteria (AC-NNN). Record the plan's path in the source: field of the output.
Phase 2 — Decompose
Break each phase into atomic tasks. Each task must be:
- One action: a single file change or closely related set
- Verifiable: clear done-when condition
- Estimated: S (< 30 min) / M (30–120 min) / L (> 2 hours)
Phase 3 — Order by Dependency
- Build dependency graph (T001 must complete before T002)
- Mark parallel-safe tasks with
[P] - Mark tasks requiring user sign-off with
[US] - Number sequentially:
T001,T002, ...
Phase 4 — Validate
- Every task maps to ≥1 requirement
- Every requirement maps to ≥1 task
- Every plan Acceptance Criterion (
AC-NNN) is covered by ≥1 task - No circular dependencies
- Size estimates on every task
Output Template
Write the task breakdown to tasks.md in the same feature folder as the source plan (docs/plans/<feature>/tasks.md), so the source: link resolves to the sibling ./plan.md.
---
source: ./plan.md
date: <YYYY-MM-DD>
---
# Task Breakdown
## Tasks
| ID | Task | Size | Depends On | Markers | Done When |
|---|---|---|---|---|---|
| T001 | <action on specific file/module> | S/M/L | — | | <verifiable condition> |
| T002 | ... | S | T001 | | ... |
| T003 | ... | M | T001 | [P] | ... |
| T004 | ... | S | T002, T003 | [US] | ... |
### Markers
- `[P]` — parallel-safe at same dependency level
- `[US]` — requires user sign-off
## Dependency Graph
T001 → T002 → T004
T001 → T003 ──┘
## Coverage Matrix
Map every plan requirement AND Acceptance Criterion to the tasks that satisfy it.
| Plan item | Tasks |
|---|---|
| REQ-001 | T001, T002 |
| AC-001 | T001, T002 |
| AC-002 | T003 |
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.
- 4d ago First seen · 84 lines · 76 tokens per session scan A 0719e8aca5f1
tasks is a skill published in the GitHub repository zexion7873/copilot-setting (1 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 761 once invoked, about $0.0004 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
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-prices
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?"…
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
az-cli
Use the Azure CLI (az) to manage Azure resources from the command line. Trigger this skill whenever the user asks to create, configure, manage, deploy, or interact with any Azure resource — even if they don't explicitly mention "az cli". Also trigger when the user asks about Azure CLI commands, syntax, or wants to…
plan-task
Create a detailed implementation plan before coding. Use when starting a new feature, multi-step refactor, or complex task. Invoked by saying "plan", "create a plan", or "plan this task".
commit
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push".