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/bugfixnpx skills add DynamoDS/DynamoHome --skill bugfixgit 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.00000 | $0.00620 |
| Opus 5 | $0.00000 | $0.00310 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
bugfix 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Workflow – DynamoHome
Use this workflow when diagnosing and fixing a bug.
Steps
1. Reproduce the issue
Before touching any code:
- Identify the affected module: Recent, Samples, Learning, Sidebar, or layout
- Check whether the bug occurs in dev mode (
npm run start) or only inside Dynamo (WebView context) - Dev-mode bugs: reproduce with mock data from
src/assets/ - WebView-only bugs: root cause is likely in
src/functions/utility.tsor a missingwindow.chrome?.webviewguard
2. Locate the root cause
Common bug locations in DynamoHome:
| Symptom | Where to look |
|---|---|
| Data not displaying | receiveXxxDataFromDotNet callback and JSON parsing in the page component |
| Localization broken / missing text | Key missing in one or more of the 14 locale files |
| Settings not persisting | saveHomePageSettings() in utility.ts and SettingsContext.tsx |
| Crash on load / outside Dynamo | Missing window.chrome?.webview optional chaining guard |
| Wrong view mode shown | SettingsContext values (recentPageViewMode, samplesViewMode) |
| Action does nothing in Dynamo | Missing await on scriptObject.* calls — all hostObjects methods are async |
3. Apply the fix
- Make the smallest change that fixes the issue — do not refactor adjacent code
- Do not change unrelated files
- If the fix touches
windowglobals or the settings JSON schema:- Global callback names must not change
- Settings field names must not change (adding new fields is safe)
4. Add a regression test
For every bug fixed, add or update a test that would have caught it:
// tests/unit/ComponentName.test.tsx
it('does not crash when graphData is empty', () => {
render(<PageRecent graphs={[]} />);
expect(screen.getByText(/no recent files/i)).toBeInTheDocument();
});
Run: npm run test:unit
5. Verify everything passes
npm run lint:check # No new lint errors
npm run test:unit # All unit tests pass (including new regression test)
npm run build # Dev bundle still builds
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 · 65 lines · 0 tokens per session scan A 43193e6a7324
bugfix is a skill published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 620 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
article-exporter
Export any web article to a local Obsidian-ready Markdown directory. Fetches page content via actionbook CLI, downloads images locally, rewrites image references to relative paths, and optionally translates the article using AI. Produces a self-contained folder with README.md, images/, and an index.md navigation file.
youtube-cli
Searches YouTube and fetches video transcripts via the cli-web-youtube command-line tool — video search, video details (views, duration, description, keywords), trending by category, channel info, and timestamped transcripts/captions with language selection and translation. Use when the user asks about YouTube…
figma-implement-design
Use to translate inspected Figma structure into a production-ready Toolcraft generated app.
snapdom
Skill "snapdom" from 2025Emma/vibe-coding-cn, covering snapdom skill, when to use this skill, key features, universal export options and performance.
design-system
Translates an image (or a set of image references — screenshots, mockups, Figma URLs, live websites) into two mirrored design-system artifacts: docs/design.md (YAML tokens + prose, following Google's open design.md format, for the coding agent) and docs/design.html (a self-contained, token-driven style guide rendering…
bilingual-paper-reader
英文論文的雙欄對照精讀工具。把 PDF 轉成逐段資料檔，由你逐段翻成貼切通順的學術中文，並用五色預先標出核心論點／創新點／方法／限制／可引用金句，再用一個可重複使用的離線 HTML 閱讀器左右對照閱讀；使用者可自己再畫螢光筆，標記存在瀏覽器可持久保存，並一鍵匯出成 Markdown 讀書筆記。閱讀器是一支、論文是資料檔，不是一篇論文一個檔。何時用：要精讀一篇英文期刊論文、想邊看邊對照中文、要標重點並留下筆記、想快速判斷這篇的貢獻與弱點在哪。觸發詞：論文翻譯、對照翻譯、雙語對照、中英對照、逐段翻譯、精讀論文、讀論文、英文論文看不懂、螢光筆、畫重點、標重點、讀書筆記、論文筆記、閱讀器、bilingual reader。與…