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 instructions/dynamods/dynamohome/claude-mdgit 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.01779 | $0.01779 |
| Opus 5 | $0.00890 | $0.00890 |
| Sonnet 5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
DynamoHome CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DynamoHome
DynamoHome is the start page for Dynamo, an Autodesk visual programming tool. It is a React 18 SPA that runs inside a Chrome WebView (Edge WebView2) embedded in the Dynamo desktop application — not in a standalone browser. It is published to npm as @dynamods/dynamo-home.
Architecture
App.tsx # IntlProvider (localization) + SettingsProvider
└── LayoutContainer.tsx # SplitPane: resizable sidebar + main content
├── Sidebar.tsx # Left nav: page switching, custom dropdowns
│ └── CustomDropDown.tsx
└── MainContent.tsx # Renders active page based on sidebar state
├── PageRecent.tsx # Recent Dynamo files — grid or table view
│ ├── GraphGridItem.tsx
│ └── GraphTable.tsx # react-table with custom cell renderers
│ ├── CustomNameCellRenderer.tsx
│ ├── CustomLocationCellRenderer.tsx
│ └── CustomAuthorCellRenderer.tsx
├── PageSamples.tsx # Sample graphs — grid or table view
│ ├── SamplesGrid.tsx → SamplesGridItem.tsx
│ └── SamplesTable.tsx → CustomSampleFirstCellRenderer.tsx
└── PageLearning.tsx # Learning resources — guides + video carousels
├── Carousel.tsx
├── GuideGridItem.tsx
├── ModalItem.tsx
└── VideoCarouselItem.tsx
src/components/Common/ # Shared across modules
CardItem.tsx Arrow.tsx Tooltip.tsx Portal.tsx CustomIcons.tsx
- No routing library — page switching is state in
MainContent.tsx - No Redux or external state — React Context (
SettingsContext.tsx) +useStateonly public/index.htmlhas two roots:#root(React) and#modal-root(Portal target)
Data flow
Dynamo (.NET host)
│ calls window globals on the app:
├─ window.receiveGraphDataFromDotNet(json) → PageRecent state
├─ window.receiveSamplesDataFromDotNet(json) → PageSamples state
├─ window.receiveTrainingVideoDataFromDotNet(json) → PageLearning state
├─ window.receiveInteractiveGuidesDataFromDotNet(json) → PageLearning state
├─ window.setLocale(locale) → re-renders with new locale
├─ window.setHomePageSettings(settingsJson) → SettingsContext hydration
└─ window.setShowStartPageChanged(show) → loading overlay
│ app calls back into Dynamo via:
└─ window.chrome.webview.hostObjects.scriptObject.* → all calls go through src/functions/utility.ts
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 · 152 lines · 1,779 tokens per session scan A eeac3d1fa832
DynamoHome CLAUDE.md is an instructions file published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It adds 1,779 tokens to every session, about $0.0089 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 instructions, from other repositories
bob-plugin-ollama-translator AGENTS.md
Instructions for CaicoLeung/bob-plugin-ollama-translator, covering repository guidelines, project overview, architecture & data flow, key directories and development commands.
xcstrings-crud CLAUDE.md
Instructions for Ryu0118/xcstrings-crud, covering xcstrings-crud, build & test, architecture, code style and key files.
codexspec CLAUDE.md
Instructions for Zts0hg/codexspec, covering claude.md - codexspec development guide, project overview, purpose, technology stack and architecture.
VI-Translate AGENTS.md
AGENTS.md instructions for breslee1707/VI-Translate, covering repository guidelines, shared knowledge, working contract and task routing.
DialectOS CLAUDE.md
Instructions for KyaniteLabs/DialectOS, covering kyanitelabs engineering rules, project-specific context, kyanitelabs engineering rules, organization principles and issue-driven development.
DialectOS AGENTS.md
Instructions for KyaniteLabs/DialectOS, covering agents.md — dialectos, public agent skill, project structure, build and testing.