Borrowing it
Nothing to install: this file belongs to groupzer0/vs-code-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/groupzer0/vs-code-agents/main/.github/skills/analysis-methodology/SKILL.mdgit clone --depth 1 https://github.com/groupzer0/vs-code-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/groupzer0/vs-code-agents/analysis-methodology)<a href="https://agentmods.dev/skills/groupzer0/vs-code-agents/analysis-methodology"><img src="https://agentmods.dev/badge/skills/groupzer0/vs-code-agents/analysis-methodology/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/groupzer0/vs-code-agents/analysis-methodology"><img src="https://agentmods.dev/badge/skills/groupzer0/vs-code-agents/analysis-methodology.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00757 |
| Opus 5.5 | $0.00000 | $0.00303 |
| Sonnet 5.5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
analysis-methodology 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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analysis Methodology
A systematic approach to converting unknowns to knowns through structured investigation.
Core Principle
Objective: Every analysis session should reduce uncertainty. If an unknown cannot be resolved, document why and what is needed to close it.
Confidence Levels
Classify every finding by its evidence strength:
| Level | Label | Meaning | Example |
|---|---|---|---|
| 1 | Proven | Verified by code execution, POC, or reproducible test. | "Running npm test -- --filter=X confirms the error." |
| 2 | Observed | Seen in logs, monitoring, or direct inspection, but not isolated. | "The error appears in production logs at 3am." |
| 3 | Inferred | Derived from documentation, patterns, or logical deduction. | "The API docs suggest this should return 404." |
Rule: Findings at Level 3 (Inferred) should be flagged for upgrade to Level 1 (Proven) before being used for decisions.
Gap Tracking Template
Use this structure to surface remaining unknowns:
## Remaining Gaps
| # | Unknown | Blocker | Required Action | Owner |
|---|---------|---------|-----------------|-------|
| 1 | Why does X fail under load? | Cannot reproduce locally. | Need staging access or load test harness. | [TBD] |
| 2 | Does API Y support pagination? | Docs unclear. | Contact vendor or run POC against sandbox. | [TBD] |
Behaviors:
- Populate this table during investigation, not just at the end.
- Surface the table to the user in chat before handoff.
- Mark items as "Resolved" (with link to finding) or "Deferred" (with rationale).
Investigation Techniques
Use these patterns to move unknowns to knowns:
Log Tracing
- Add targeted logging to isolate behavior.
- Compare expected vs actual log sequences.
Component Isolation
- Reproduce behavior with minimal dependencies.
- Use mocks/stubs to eliminate variables.
Binary Search Debugging
- Narrow the failure window by bisecting commits, config changes, or code paths.
- Halve the search space with each step.
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.
- 1mo ago First seen · 94 lines · 0 tokens per session scan A 52e30e03bdad
analysis-methodology is a skill published in the GitHub repository groupzer0/vs-code-agents (292 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 757 tokens. 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…