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 commands/hmake98/nestjs-starter/reviewgit clone --depth 1 https://github.com/hmake98/nestjs-starterWrote 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/commands/hmake98/nestjs-starter/review)<a href="https://agentmods.dev/commands/hmake98/nestjs-starter/review"><img src="https://agentmods.dev/badge/commands/hmake98/nestjs-starter/review.svg" alt="Measured on agentmods" 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.00762 |
| Opus 5 | $0.00000 | $0.00381 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the following code or file for quality, correctness, and adherence to this project's conventions: $ARGUMENTS
Read the file(s) being reviewed carefully. Then check against every rule below.
Checklist
Module structure
- Feature module imports
DatabaseModuledirectly — notUserModuleor another feature module - No circular imports between feature modules
- Module only exports what other modules actually need
-
CommonModuleis only imported byAppModule
Services
- All errors thrown as
HttpExceptionwith an i18n key string andHttpStatusconstant — never a raw string message - Existence checks use a private
assertExistshelper, not inline guards - No direct
process.envaccess — useConfigService.getOrThrow<T>(key) -
@Injectable()decorator present - No business logic in controllers — controllers only delegate to services
Controllers
-
@ApiTags,@ApiBearerAuth('accessToken')present on class - Every method has
@ApiEndpoint({ summary, messageKey })— no bare HTTP decorators without doc - Admin controllers have
@AllowedRoles([UserRole.ADMIN])at class level - Public routes have
@PublicRoute()— not missing auth bypass - Controllers return service result directly — no manual response shaping
DTOs
- Response DTOs:
@Expose()on every included field,@Exclude()on sensitive fields (passwordHash etc.) - Response DTOs have
@ApiPropertywith afakerexample on each field - Input DTOs have
class-validatordecorators on every field - Update DTOs have all fields
@IsOptional() - No
anytypes
Repository
- Only Prisma calls — no raw SQL unless necessary
-
findUniquewithselect: { id: true }for existence checks (notfindFirst) - Soft delete sets
deletedAt: new Date()— not a hard delete - Returns typed entity interfaces — not raw Prisma results with
as any
Guards & decorators
-
@PublicRoute()used only where truly public — health check and auth endpoints -
@AllowedRolesreceives an array, not a spread
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.
- 5d ago First seen · 67 lines · 0 tokens per session scan A a8cbdd7e41a3
review is a command published in the GitHub repository hmake98/nestjs-starter (61 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 762 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-30.
Other commands, from other repositories
feature
Post a feature to the Features Board on production and write tweets.
commit-all
Group all changes semantically and commit each group separately.
querying
Query documents from a search index using type-safe filters with support for pagination, sorting, field selection, scoring, and highlighting. Count matching documents efficiently without returning results.
index-management
Create, inspect, and drop search indexes. Wait for indexing to complete after data changes. Indexes automatically track Redis keys matching a specified prefix.
create-pr
Create a pull request following the official template.
pr-plan
Analyze a JIRA ticket and create a detailed implementation plan.