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/ndthanhdev/mcp-browser-kit/hexagonal-inversify-dinpx skills add ndthanhdev/mcp-browser-kit --skill hexagonal-inversify-digit clone --depth 1 https://github.com/ndthanhdev/mcp-browser-kitWhat 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.00075 | $0.03266 |
| Opus 5 | $0.00037 | $0.01633 |
| Sonnet 5 | $0.00015 | $0.00653 |
| Haiku 4.5 | $0.00007 | $0.00327 |
Grade A, and why
hexagonal-inversify-di 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.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hexagonal + InversifyJS DI Pattern
This monorepo uses Hexagonal architecture (Ports & Adapters) wired with InversifyJS. Every package's role is encoded in its name prefix, and dependency wiring follows a strict, repeatable recipe.
When to Use This Skill
Load this skill when the task involves:
- Creating a new package under
packages/ - Adding or modifying a port (interface + token) in a
core-*package - Implementing a use case inside
core-* - Implementing a driven (secondary) or driving (primary) adapter
- Editing an app composition root (
apps/*/src/services/container.ts,apps/*/src/bootstrap-*.ts,apps/*/src/main.ts) - Any question about
@injectable,@inject,Container, bindings, or scopes in this repo
Architecture Map
| Prefix | Role | May depend on |
|---|---|---|
core-* |
Domain. Use cases + port definitions (input-ports/, output-ports/) |
types, core-utils |
*-driving-* |
Primary adapter. Drives the core inward (e.g. HTTP/MCP/RPC entrypoints) | relevant core-*, types, helper-* |
*-driven-* |
Secondary adapter. Driven by the core outward (DBs, external services, loggers) | relevant core-*, types, helper-* |
helper-* |
Shared utilities/mixins used by adapters | types |
types |
Pure type-only contracts. No DI, no runtime code. | nothing |
Rule of thumb: adapters depend on core-* (where the port lives), never directly on types when a port exists. Core depends only on types and core-utils.
Core Conventions
1. DI library
- InversifyJS +
reflect-metadata - Import
reflect-metadataonce per runtime entrypoint (already handled in existing apps)
2. Dual identifier trick (ports)
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 · 326 lines · 75 tokens per session scan A 4fb9aebb668f
hexagonal-inversify-di is a skill published in the GitHub repository ndthanhdev/mcp-browser-kit (54 stars, last pushed 8d ago), licensed MIT. It adds 75 tokens to every session and 3,266 once invoked, about $0.0004 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-30.
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…