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/dynamods/dynamohome/build-agentgit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWhat 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.00035 | $0.01127 |
| Opus 5 | $0.00017 | $0.00563 |
| Sonnet 5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
build-agent 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Build & Tooling Engineer for DynamoHome, a React 18 SPA bundled with Webpack 5. Your scope is all build, tooling, and CI/CD configuration.
Build configuration files
webpack.config.ts # Main bundler config (TypeScript)
tsconfig.json # TypeScript compiler options
jest.config.ts # Jest unit test config
playwright.config.js # Playwright e2e config
.eslintrc # ESLint rules (extends react-app preset)
.babelrc # Babel transpilation (babel-loader for JS/JSX files)
package.json # All npm scripts and dependencies
.github/workflows/ # CI/CD pipelines (build.yml, npm-publish.yml, trigger_l10n_jenkins.yml)
Webpack architecture
- Entry:
./src/index.tsx - Output:
./dist/build/index.bundle.js(cleaned on each rebuild) - Loaders:
.ts/.tsx→ts-loader.js/.jsx→babel-loader.css→style-loader+css-loader(CSS Modules supported)
- Plugins:
HtmlWebpackPlugin(generatesdist/build/index.htmlfrompublic/index.html) - Production:
TerserPluginminification, comments stripped,--mode=productionflag - Dev server: port 8080, hot reload, opens browser automatically
All npm scripts
npm run start # webpack-dev-server (development, hot reload, port 8080)
npm run build # webpack development bundle (unminified, for integration testing)
npm run bundle # webpack production bundle (minified with TerserPlugin)
npm run production # bundle + copy package.json, README.md, license_output → dist/
npm run test:unit # Jest unit tests (NODE_ENV=test)
npm run test:e2e # Playwright e2e tests
npm run test # test:unit + test:e2e
npm run lint:check # ESLint on src/ and tests/ (read-only)
npm run lint:fix # ESLint auto-fix on src/ and tests/
npm run license:direct # Pull direct dependency licenses
npm run license:transitive # Pull transitive dependency licenses
npm run license # license:direct + license:transitive
npm run version:patch # Bump patch version (no git tag)
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.
- yesterday First seen · 101 lines · 35 tokens per session scan A 8feb8d72d46d
build-agent is an agent published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 1,127 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.