Borrowing it
Nothing to install: this file belongs to DynamoDS/DynamoHome. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DynamoDS/DynamoHome/master/.claude/skills/bugfix/SKILL.mdgit 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/bugfix)<a href="https://agentmods.dev/skills/dynamods/dynamohome/bugfix"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/bugfix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dynamods/dynamohome/bugfix"><img src="https://agentmods.dev/badge/skills/dynamods/dynamohome/bugfix.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00620 |
| Opus 5.5 | $0.00000 | $0.00248 |
| Sonnet 5.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 2mo 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 — 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.
- 2mo ago First seen · 65 lines · 0 tokens per session scan A 43193e6a7324
bugfix is a skill published in the GitHub repository DynamoDS/DynamoHome (3 stars, last pushed 11d 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
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…