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/retz8/pastiche/pick-up-tasknpx skills add retz8/pastiche --skill pick-up-taskgit clone --depth 1 https://github.com/retz8/pasticheWrote 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/retz8/pastiche/pick-up-task)<a href="https://agentmods.dev/skills/retz8/pastiche/pick-up-task"><img src="https://agentmods.dev/badge/skills/retz8/pastiche/pick-up-task.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.00060 | $0.00512 |
| Opus 5 | $0.00030 | $0.00256 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
pick-up-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 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.
What it actually says
pick-up-task
Harness conventions: _dev/docs/harness.md. Run from the pastiche repo root.
Workflow
-
Identify the task. Read
_dev/TODO.md. Tasks are numbered lines (- [ ] **N.** Name — …) under version-group headings. If the user named a task, use it; otherwise list unchecked, non-[WIP]tasks and ask. Respect group order — earlier groups first unless the user overrides. -
New or resume? A task already marked
[WIP]whose feature branch exists → resume. Otherwise → new. -
New task:
- Edit
_dev/TODO.md: insert[WIP]after- [ ]on the task line. - Branch off main:
git checkout main && git pull && git checkout -b <version>/<task-name>—<version>from the group heading (e.g.1.1.0),<task-name>kebab-cased short name (e.g.1.1.0/codex-support). - Tell the user the next step is
grill-me→grill-to-spec→divide-task. Do not start it yourself.
- Edit
-
Resume:
- If the current branch is not the task's feature branch, switch to it.
- Always run the
rebase-feat-with-mainskill (absorbs any hotfixes). - Report where the task stands (spec present at
_dev/docs/<branch>/? sub-tasks divided?).
-
Stop. Pickup ends here; the user drives what happens next.
Notes
[WIP]is a soft lock across parallel sessions — never strip another session's marker.- For live parallel work on sub-tasks, create a worktree off the feature branch instead of switching branches; skip the worktree when the user says to work directly on the current branch.
- Completion (not this skill's job): checkbox ticked,
[WIP]removed, and parent issue closed when the feature branch merges to main.
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 · 33 lines · 60 tokens per session scan A 1ddd2bf806a9
pick-up-task is a skill published in the GitHub repository retz8/pastiche (4 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 512 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
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…