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/lensapp/lens-sandbox/problem-first-implnpx skills add lensapp/lens-sandbox --skill problem-first-implgit clone --depth 1 https://github.com/lensapp/lens-sandboxWrote 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/lensapp/lens-sandbox/problem-first-impl)<a href="https://agentmods.dev/skills/lensapp/lens-sandbox/problem-first-impl"><img src="https://agentmods.dev/badge/skills/lensapp/lens-sandbox/problem-first-impl.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.00083 | $0.01555 |
| Opus 5 | $0.00042 | $0.00777 |
| Sonnet 5 | $0.00017 | $0.00311 |
| Haiku 4.5 | $0.00008 | $0.00155 |
Grade A, and why
problem-first-impl 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 today.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec — Problem-First → Implementation
Take the agreed problem + Gherkin scenarios from /problem-first and move to technical planning. This skill does two things: (1) a final scope confirmation against the product docs and existing specs, and (2) hand-off — writing the .feature file and entering plan mode.
This skill is the "code path" continuation. If the goal is to file an issue for someone else to pick up, use /problem-first-issue instead.
Inputs
You need the full output of a /problem-first session, or a GitHub issue carrying the same content:
- A problem statement (1-2 sentences).
- An agreed set of Gherkin scenarios.
- A target crate in this monorepo.
- An agreed approach — one-paragraph solution direction from
/problem-firstPhase 3. - Alternatives considered and their rejection reasons (1-3).
- Optionally: assumptions / constraints, non-goals, open questions.
Invocation modes
Mode A — Continuation in the same session as /problem-first.
If /problem-first just ran in this conversation, read the full output (problem, scenarios, target crate, approach, alternatives, assumptions) directly from conversation context. Doc-level alignment was confirmed at intake — do not re-run that check. Briefly confirm: "Using the problem, N scenarios, target crate <crate>, and chosen approach from the /problem-first session above (doc-alignment confirmed) — proceeding to code-level check."
Mode B — Standalone (picking up a GitHub issue, or resuming cold).
If there is no prior /problem-first output in the session, the user is likely picking up work that was planned earlier. Either:
- Ask for the source: "Do you have a
/problem-first-issueGitHub issue for this? Paste the number or URL and I'll read it (gh issue view <n>), or paste the problem + scenarios + approach directly." - Or elicit all six input items above.
In Mode B, product docs may have changed since the issue was filed. Re-run the doc-level alignment check from /problem-first Phase 4 before the code-level check — cheap insurance against silently implementing against stale direction.
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.
- today Changed · -9 lines a702846bbf04
- 4d ago First seen · 99 lines · 83 tokens per session scan A 19ed18de9e7b
problem-first-impl is a skill published in the GitHub repository lensapp/lens-sandbox (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 83 tokens to every session and 1,555 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
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…