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/dynamods/dynamohome/build-toolingnpx skills add DynamoDS/DynamoHome --skill build-toolinggit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWrote 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/dynamods/dynamohome/build-tooling)<a href="https://agentmods.dev/skills/dynamods/dynamohome/build-tooling"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/build-tooling.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.00000 | $0.00844 |
| Opus 5 | $0.00000 | $0.00422 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
build-tooling 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build and Tooling Skills – DynamoHome
Bundler: Webpack 5
webpack.config.ts is the single source of truth for all bundling.
Key configuration
Entry: src/index.tsx
Output: dist/build/index.bundle.js ← path is hardcoded in Dynamo, do NOT change
Loaders: ts-loader (TS/TSX), babel-loader (JS/JSX), css-loader + style-loader (CSS)
Plugins: HtmlWebpackPlugin → dist/build/index.html
Modes: development (unminified) | production (TerserPlugin minification)
Build commands
npm run start # webpack-dev-server, port 8080, hot reload
npm run build # dev bundle (webpack --mode=development)
npm run bundle # production bundle (webpack --mode=production, minified)
npm run production # bundle + copy package.json, README.md, license_output → dist/
TypeScript: tsconfig.json
Critical settings to preserve:
"strict": false— enabling this breaks existing code; do not change without explicit user approval"resolveJsonModule": true— required forimport messages from './locales/en.json'"typeRoots": ["./types", "./node_modules/@types"]— custom types loaded fromtypes/index.d.ts"jsx": "react-jsx"— no need forimport React from 'react'in components
ESLint: .eslintrc
- Extends
react-apppreset - Covers
src/andtests/ - Run:
npm run lint:check(read-only),npm run lint:fix(auto-fix) - Must pass before any PR merge
Jest: jest.config.ts
- Preset:
ts-jest - Environment:
jsdom - Coverage from:
src/**/*.{ts,tsx}, output to./coverage/ - Setup file:
tests/jest.setup.ts— applies chrome global mocks - Module name mapper: CSS →
identity-obj-proxy, images →fileMock.ts - Unit test files live in:
tests/unit/ - Run:
npm run test:unit
Playwright: playwright.config.js
- Chromium only
testDir: './tests/e2e'— scoped to e2e tests only- Web server: auto-starts
npm startbefore tests, waits for port 8080 - CI: 1 worker, 2 retries; local: unlimited workers, 0 retries
- Run:
npm run test:e2e(targets all*.spec.tsfiles intests/e2e/)
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 · 75 lines · 0 tokens per session scan A 59d9b2b0118f
build-tooling is a skill published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 844 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-31.
Other skills, from other repositories
integrated-browser
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.
agent-host-e2e-tests
Use when writing, recording, updating, validating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a…
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
deepagents-thread-inspector
Inspect and explain conversations in the local Deep Agents Code SQLite session store. Use as a fallback when LangSmith trace tooling is unavailable, for offline or untraced sessions, or when asked to identify or summarize a local dcode thread, inspect checkpoint metadata, list recent local threads, or parse…
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…