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/code-reviewnpx skills add DynamoDS/DynamoHome --skill code-reviewgit 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.01138 |
| Opus 5 | $0.00000 | $0.00569 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
code-review 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skills – DynamoHome
Review mindset
Focus on real problems: regressions, missing tests, broken localization, type safety gaps, Dynamo integration breakage. Do not request style changes or refactors for code not touched by the PR. Keep feedback concise and actionable.
Review process
1. Understand the scope
Read the PR description and list of changed files. Identify:
- Which module(s) are touched: Recent, Samples, Learning, Sidebar, Common, build, tests
- Whether it is a feature, bugfix, refactor, or dependency update
- Any Dynamo integration touchpoints (window globals, settings schema, output path)
2. Work through the checklist
See checklist below. Flag blockers as you go; note recommendations separately.
3. Verify test coverage
- New/modified components have unit tests in
tests/unit/ - Changed user flows have Playwright coverage
tests/e2e/*.spec.tsfiles contain no selectors or direct page actions
4. Check build integrity
Confirm (or ask the author to confirm):
npm run lint:check # Passes
npm run test:unit # Passes
npm run build # Dev bundle succeeds
npm run bundle # Production bundle succeeds (only for PRs touching webpack or build scripts)
5. Write structured feedback
See "How to give feedback" section below.
Checklist
TypeScript
- No new
anytypes introduced for props, state, or function parameters - No
// @ts-ignoreadded - New types are interfaces (not inline) if used in more than one place
- Existing
anyin legacy code (SettingsContext,utility.ts) is not flagged as new issues
React components
- Functional components only (no class components)
- Explicit prop interfaces defined
- CSS classes use
styles['class-name']from CSS Modules imports — no global classNames or inline styles - No new UI or state management libraries added to
package.json
Localization
- Every new user-visible string has a key in
src/locales/en.json - The same key exists in all 13 other locale files (
cs,de,es,fr,it,ja,ko,pl,pt-BR,ru,zh-Hans,zh-Hant) - Keys follow
module.element.descriptorformat - No hardcoded text in JSX (no raw string children, no
title=""without intl)
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 · 109 lines · 0 tokens per session scan A 9a13e8d7c24e
code-review 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 1,138 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
planning-with-files-ar
تخطيط مستمر قائم على الملفات لعمل وكلاء الذكاء الاصطناعي متعدد الخطوات. يحتفظ بملفات taskplan.md و findings.md و progress.md على القرص، وتحقن خطافات دورة الحياة سياق التخطيط المحدد للمشروع. تقرأ الاستعادة التلقائية ملفات تخطيط المشروع فقط. يمكن للأمر الصريح session-catchup.py --metadata فحص بيانات وصفية لجلسات الوكيل…
kl-consistency-test
Write, calibrate, and debug the prefill-vs-decode logprob (KL) consistency tests in sglang -- the two independent conditions a zero requires (every operator batch-invariant, and the two paths computing the same function), which helper separates them, how to pick a threshold once they hold, and how to localize a…
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.