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/tikoci/rosetta/pick-next-tasknpx skills add tikoci/rosetta --skill pick-next-taskgit clone --depth 1 https://github.com/tikoci/rosettaWhat 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.00048 | $0.00605 |
| Opus 5 | $0.00024 | $0.00302 |
| Sonnet 5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
pick-next-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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pick Next Task
The agent's what now? verb. Reads the GitHub Issues queue and returns the next pickable
issue with enough context to start work. (Named for the retired tasks/ file queue — the
verb survives, the backend is now issues; see tasks/README.md.)
When to use
- Starting a new work session and asking "what's the next thing?"
- Picking up rosetta after a break
What "pickable" means
An issue is pickable when:
- It is open and labeled
agent-ready— acceptance criteria are settled. - It is not labeled
blockedand its body names no unresolved "blocked on" issue. - It is not labeled
umbrella— umbrellas track themes; work happens in child issues.
Procedure
-
List candidates.
gh issue list --state open --label agent-ready --json number,title,labels,updatedAtIf a filter argument was supplied, match it against titles and labels.
-
If none are agent-ready, widen with
gh issue list --state open --json number,title,labels,body(thebodyfield is what holds "blocked on" references and umbrella checklists) and report what exists instead: discussion-stage issues (unlabeled — could be settled into readiness),blockedissues (say what each waits on), andumbrellaissues (their child checklists show what could be spawned next). Also point atBACKLOG.mdInbox and openbriefings/. -
Surface the top pick.
gh issue view <n> --comments, then present: number, title, acceptance criteria,V-*validation rows, and linked briefings or archivedtasks/done/T-*.mdfiles — some issues keep their full spec in the archived task file (e.g. #26 →T-0038), so read those too. -
Remind the close discipline. The eventual PR must say
Closes #<n>in its body; partial landings spawn follow-up issues before merge (issue-pr-linking.instructions.md).
What this skill does NOT do
- Assign the issue or open PRs — that happens when work actually starts.
- Create new issues — that's
promote-idea. - Run validation checks — that's
verify-task.
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.
- 3d ago First seen · 56 lines · 48 tokens per session scan A 42d1f0559cd1
pick-next-task is a skill published in the GitHub repository tikoci/rosetta (43 stars, last pushed 17d ago), licensed MIT. It adds 48 tokens to every session and 605 once invoked, about $0.0002 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-30.
Other skills, from other repositories
debug-remote
Attach to a running Windows process through a WinDbg debug server and inspect it live. Use when the user wants to debug a process on another machine, or one already under a .server session, rather than a crash dump.
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
forecast
Build a forecast dashboard in monday — committed, best-case, and pipeline views by close month, rendered as real dashboard widgets. Use when someone says "build me a forecast", "show me Q2 pipeline", "Salesforce-style forecast", "forecast dashboard", "commit vs best-case", "what's our number this quarter", "how are we…
run-sequence
Manage CRM sequences end-to-end — list, create, enroll contacts, activate/deactivate, duplicate, and track performance. Use when someone says "what sequences do I have", "create a welcome sequence", "enroll this contact in a sequence", "add these leads to my nurture sequence", "deactivate the cold outreach sequence"…
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
update-change-log
To synchronize CHANGELOG.md with changes made last week (mon - sun).