agentmods.dev

dev-context-analysis

dev-context-analysis is a skill for Claude Code from cicababba/claude-plugins-marketplace. It costs 40 tokens per session (815 once invoked), scanned A, original, MIT.

A code-analysis phase examines selected files or folders to document their patterns, dependencies, tests, and current implementation details. It saves the findings in a context-analysis.md file.

In plain words
What is it for?
Use it at the start of a development session or when given specific paths to inspect. It helps map code conventions, imports, related tests, and the behavior of key functions, classes, and data structures.
Why use it?
It gives developers a shared understanding of existing code before requirements or implementation planning begin. It avoids changing source files while the code is being studied.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dev-workflow-automation plugin — 9 skills, 4 commands, 11 agents shipped together

not rated 3repo 9mo ago A scan 40 tokens original MIT

Good fit Use it at the start of a development session or when given specific paths to inspect. It helps map code conventions, imports, related tests, and the behavior of key functions, classes, and data structures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cicababba/claude-plugins-marketplace/dev-context-analysis
View source ↗ cicababba/claude-plugins-marketplace
Install

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.

Any agent
npx skills add cicababba/claude-plugins-marketplace --skill dev-context-analysis
Clone the repo
git clone --depth 1 https://github.com/cicababba/claude-plugins-marketplace

Made for: Claude Code.

Or install dev-workflow-automation, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 11 agents.

Wrote 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.

agentmods badge for dev-context-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-context-analysis.svg)](https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-context-analysis)
Your own site
<a href="https://agentmods.dev/skills/cicababba/claude-plugins-marketplace/dev-context-analysis"><img src="https://agentmods.dev/badge/skills/cicababba/claude-plugins-marketplace/dev-context-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 815 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00815
Opus 5 $0.00020 $0.00407
Sonnet 5 $0.00008 $0.00163
Haiku 4.5 $0.00004 $0.00081

Measured 7d ago against content hash 31529166bbd3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

dev-context-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 7d 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.

dev-workflow-automation/skills/dev-context-analysis/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Context Analysis

This skill performs the context analysis phase of a development session.

When to Use

  • At the start of /init after session creation
  • When the user provides paths to analyze
  • When you need to understand existing code patterns before specification gathering

Input

  • sessionPath: Path to the current session directory
  • paths: List of file or folder paths to analyze (e.g., /src/auth, /src/models/user.ts)

Responsibilities

  • For each provided path, analyze:
    • Existing Patterns: Code conventions, architectural patterns, naming conventions
    • Dependencies & Imports: External packages, internal modules, dependency graph
    • Related Tests: Test files, test patterns, coverage areas
    • Current Implementation Details: Key functions, classes, data structures
  • Build a structured per-path analysis
  • Generate context-analysis.md with organized findings
  • Save via artifact-fs-manager skill

MUST NOT

  • Propose implementation steps or planning
  • Generate a "Plan", "Roadmap", or "Implementation" section
  • Modify any source code files
  • Make assumptions about what should be changed
  • Skip paths or provide incomplete analysis

Process

Step 1: Validate Paths

  1. For each provided path:
    • Verify the path exists
    • Determine if it's a file or directory
    • Report any invalid paths to the user

Step 2: Analyze Each Path

For each valid path, spawn analysis (can be parallelized):

  1. Scan for patterns:

    • Code style conventions
    • Architectural patterns (MVC, Clean Architecture, etc.)
    • Naming conventions (camelCase, PascalCase, etc.)
    • Common utilities and helpers used

  2. Extract dependencies:

    • External package imports
    • Internal module imports
    • Circular dependency detection
    • Version constraints if visible

  3. Find related tests:

    • Corresponding test files (*.test.ts, *.spec.ts)
    • Test patterns used (unit, integration, e2e)
    • Mocking strategies
    • Coverage gaps

Read the full file on GitHub · 146 lines

Changes

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.

  1. 7d ago First seen · 146 lines · 40 tokens per session scan A 31529166bbd3

Subscribe to this mod's changes

dev-context-analysis is a skill published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 815 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.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens