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/flurdy/agent-skills/implement-solutionnpx skills add flurdy/agent-skills --skill implement-solutiongit clone --depth 1 https://github.com/flurdy/agent-skillsWhat 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.00054 | $0.02081 |
| Opus 5 | $0.00027 | $0.01040 |
| Sonnet 5 | $0.00011 | $0.00416 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
implement-solution 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 2d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Solution
Implement the smallest maintainable solution that meets the requested outcome. Apply strong engineering judgment before and during coding without replacing the model's native coding ability with a principle checklist.
This is a bounded premium/high implementation route. Select it dynamically when a task is implementation-ready but material local engineering judgment makes stronger configured capability worthwhile. Explicit invocation also opts in. It is not an always-on gate and should not add ceremony when the repository already makes the right change obvious.
When to Use
Use this skill when requirements and any required diagnosis are sufficiently clear, and one or more of these conditions applies:
- multiple plausible local approaches remain and repository consensus should decide between them;
- changed behavior crosses interacting components, state transitions, or meaningful edge and failure paths;
- a present responsibility, dependency, duplication, or mutation trade-off materially affects maintainability or correctness;
- an implementation already in progress needs substantive simplification rather than mechanical cleanup; or
- the user explicitly invokes
/implement-solutionor requests a premium or strongest-capability implementation pass.
Do not route through it merely because a request changes code, contains the word "implement," or asks for simplicity. Skip mechanical edits and changes with one obvious established pattern. Use /diagnose-bug while the cause is unknown and /architect when consequential design decisions remain unresolved.
Boundaries
/architectowns ambiguous, high-blast-radius, security-sensitive, public-contract, migration, and hard-to-reverse decisions. Escalate rather than making those decisions under the banner of simplicity./diagnose-bugowns evidence-led diagnosis when the cause of an observed failure is unknown. Return here once the cause and verification contract are established./pedantic-reviewis the post-implementation craft review. This skill shapes the implementation proactively but does not duplicate that report./verify-taskverifies that finished work meets its requirements and has enough coverage./clean-codeowns whole-codebase formatting, linting, and warning cleanup. This skill keeps its own change clean without broadening scope to unrelated warnings.
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.
- 2d ago First seen · 175 lines · 54 tokens per session scan A 4d138bc42330
implement-solution is a skill published in the GitHub repository flurdy/agent-skills (7 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 2,081 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
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…