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/leifericf/agentic-sdk/pick-featurenpx skills add leifericf/agentic-sdk --skill pick-featuregit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/pick-feature)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/pick-feature"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/pick-feature.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.00012 | $0.00440 |
| Opus 5 | $0.00006 | $0.00220 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
pick-feature 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.
What it actually says
pick-feature
Select the best next feature from the backlog and triage the inbox as part of selection. Optimize for the smallest user-visible value with low risk and clear acceptance criteria.
Procedure
- Read
product-backlog.md,product-requirements.md,decision-log.md, andopen-questions.md(the latter three if present). If the backlog is missing or empty, returnblocked: no backlog. - Surface and resolve any
[Blocking]item affecting backlog selection before proceeding. - Triage the inbox: promote zero to two clearly apt items into
Now / Next, move clearly lower-priority items toLater, leave vague items. Rewrite unclear titles into plain user-facing language. KeepNow / Nextshort and ordered;In product (shipped)stays plain capability names. - Ask a short batch of prioritization questions, at most three, tailored to the backlog items: the outcome to optimize for, sequencing and prerequisite constraints (not timelines), and the preferred shape of the first increment (thin vertical slice versus foundation-first). Where you can derive three to five mutually exclusive options from the backlog, present them as choices; always include "write your own" and "can't answer".
- Present a shortlist of two to five items from
Now / Next, each with a one-line rationale and any risk or dependency note. Prefer the smallest user-visible value, the lowest risk, and the clearest acceptance criteria. - Confirm the selection with the user. Write the triaged backlog back to
product-backlog.md.
Boundaries
Owns selecting the next item and triaging the inbox. create-backlog owns the initial backlog; plan-feature owns decomposing the chosen item. Reached by plan-system.
Return
One line: the selected feature and the triage applied, or blocked: <reason>.
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 · 45 lines · 12 tokens per session scan A 81e8a3533f39
pick-feature is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 440 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…