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/tomzx/agents/create-existing-solutionsnpx skills add tomzx/agents --skill create-existing-solutionsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-existing-solutions)<a href="https://agentmods.dev/skills/tomzx/agents/create-existing-solutions"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-existing-solutions.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.00041 | $0.01048 |
| Opus 5 | $0.00020 | $0.00524 |
| Sonnet 5 | $0.00008 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
create-existing-solutions 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Existing Solutions Survey
Surveys existing solutions that already solve part or all of what the feature needs, before committing to a design. The goal is twofold: avoid reinventing what already exists, and harvest proven approaches as a source of information even when we end up building our own.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. .sdlc/features/N-<slug>/requirements.md(must have passed review with findings verdictapproved), or a requirements document provided in context or as a file path ($1)
Steps
- Read the requirements document and extract what the feature must do (functional requirements) and the quality attributes it must satisfy (non-functional requirements).
- Define the search scope: the categories below, plus any project-specific sources noted in
.sdlc/context/. - Search each category for candidates:
- Existing code in this repository or organization that already does something similar (search the codebase first, it is the cheapest to adopt).
- Open-source libraries, frameworks, and tools.
- Commercial or SaaS products.
- Standards, protocols, and specifications.
- Reference material: articles, papers, and write-ups describing how others solved this problem.
- For each candidate, capture what it is, its license, its maturity, and how it maps to the requirements (which FR/NFR it covers and which it leaves as gaps).
- Evaluate the strongest candidates: strengths, weaknesses, integration effort, cost, and risks (license, maintenance, security, lock-in).
- Recommend a direction (adopt, adopt and extend, build, or hybrid) with a rationale tied to the requirements.
- Record the sources of information worth borrowing from even if we do not adopt the solution (patterns, data models, edge cases they handle, pitfalls they document).
- Flag open questions where the evaluation is uncertain or needs validation.
- Write the output to
.sdlc/features/N-<slug>/existing-solutions.md.
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 · 81 lines · 41 tokens per session scan A ebbea20aee52
create-existing-solutions is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,048 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-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…