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 agents/0xfurai/claude-code-subagents/webpack-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/webpack-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/webpack-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/webpack-expert.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.1 | $0.00022 | $0.00412 |
| Opus 5 | $0.00011 | $0.00206 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
webpack-expert 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.
What it actually says
Focus Areas
- Webpack configuration settings
- Loaders and plugins for transforming and bundling assets
- Code splitting and dynamic imports
- Module resolution and aliasing
- Output management and path configuration
- Environment variables and mode configurations
- Dependency management and tree-shaking
- Handling CSS and other assets with loaders
- Source maps and debugging patterns
- DevServer setup and hot module replacement
Approach
- Analyze project requirements and plan Webpack configurations
- Choose the optimal loaders and plugins for tasks
- Implement code splitting to improve load times
- Set up module resolution to simplify imports
- Manage output directory and path configurations effectively
- Use DefinePlugin for environment variables and mode settings
- Optimize dependencies with tree-shaking techniques
- Utilize CSS loaders for efficient styles management
- Configure source maps for effective debugging
- Implement Webpack.DevServer for local development
Quality Checklist
- Ensure Webpack config files are modular and maintainable
- Validate loader and plugin configurations for correctness
- Check code splitting to ensure chunks load as expected
- Verify module resolutions to prevent import errors
- Confirm output paths match the desired structure
- Ensure environment-specific settings are correctly applied
- Check dependency optimization via tree-shaking
- Review CSS handling to ensure correct styles are loaded
- Validate source maps are correctly generated and usable
- Verify DevServer configuration functions smoothly
Output
- Comprehensive Webpack configuration files
- Loaders and plugins set up and functioning correctly
- Efficiently split code with dynamic imports
- Correct module resolution paths in configurations
- Properly managed output directories and files
- Environment variables and build modes applied
- Optimized dependency trees with minimized bundles
- Correctly compiled and loaded CSS assets
- Generated source maps for easier debugging
- Fully configured local development server with HMR
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 · 57 lines · 22 tokens per session scan A 272844398953
webpack-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 412 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-09-03.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.