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/douglance/sdlc-plugin/feasibility-analysisnpx skills add douglance/sdlc-plugin --skill feasibility-analysisgit clone --depth 1 https://github.com/douglance/sdlc-pluginWrote 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/douglance/sdlc-plugin/feasibility-analysis)<a href="https://agentmods.dev/skills/douglance/sdlc-plugin/feasibility-analysis"><img src="https://agentmods.dev/badge/skills/douglance/sdlc-plugin/feasibility-analysis.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.00022 | $0.00407 |
| Opus 5 | $0.00011 | $0.00204 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
feasibility-analysis 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
Use lifecycle-documentation only when the result needs a durable artifact or handoff.
Scout the problem space and map the landscape. Find what already exists, how others solve this, and what could make it hard or impossible. Explore wide before going deep — survey many options, don't tunnel on the first.
Use the codebase, Context7, and web search together. Every claim you make must trace to a source.
When rules, exceptions, adapters, or compensating processes appear to protect a questionable model, run find-simplifying-insight. Keep the current model as the null hypothesis and require a falsifiable prediction before recommending a paradigm shift.
What to investigate
- Existing solutions — libraries, tools, and prior art in this codebase and the wider ecosystem.
- Patterns and anti-patterns — how this problem is solved well, and the ways it's solved badly.
- Constraints — technical limits, performance bounds, compatibility, security, licensing.
- Trade-offs — for each viable option, what you gain and what you give up.
Depth
Default to WIDE reconnaissance — breadth over depth. Go DEEP on a specific option only when asked. If you've spent more time than the question warrants, stop and report what you have.
What to produce
A scout report: the landscape, viable options with their trade-offs, the key constraints, open questions, and red flags. Mark your confidence and cite the source for every finding. Say what you couldn't determine rather than guessing.
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 · 41 lines · 22 tokens per session scan A a1bf7d37685a
feasibility-analysis is a skill published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 407 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…