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/explaingit clone --depth 1 https://github.com/hmake98/nestjs-starterWhat 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.00476 |
| Opus 5 | $0.00000 | $0.00238 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
explain 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.
What it actually says
Explain how the following works in this NestJS codebase: $ARGUMENTS
Before answering, read the relevant source files so your explanation is grounded in actual code, not general NestJS knowledge.
Use this map to find the right files quickly:
| Topic | Files to read |
|---|---|
| Request lifecycle | src/common/request/request.module.ts, src/common/request/guards/jwt-access.guard.ts, src/common/request/guards/roles.guard.ts, src/common/response/interceptors/response.interceptor.ts, src/common/response/filters/response.exception.filter.ts |
| Auth flow | src/modules/auth/services/auth.service.ts, src/modules/auth/providers/jwt-access.strategy.ts, src/modules/auth/providers/jwt-refresh.strategy.ts |
| Module wiring | src/app/app.module.ts, src/common/common.module.ts, src/common/database/database.module.ts |
| Database / Prisma | src/common/database/services/database.service.ts, prisma/schema.prisma, prisma/prisma.config.ts |
| Response shaping | src/common/response/interceptors/response.interceptor.ts, src/common/response/services/response.serializer.service.ts, src/common/response/dtos/response.success.dto.ts |
| Error handling | src/common/response/filters/response.exception.filter.ts, src/common/message/services/message.service.ts |
| Caching | src/common/cache/services/cache.service.ts, src/common/cache/cache.module.ts |
| Logging | src/common/logger/services/logger.service.ts, src/main.ts |
| API docs | src/common/doc/decorators/doc.api-endpoint.decorator.ts, src/swagger.ts |
| Docker setup | Dockerfile, docker-compose.yml, docker-entrypoint.sh |
| Testing patterns | test/modules/user.service.spec.ts, test/modules/auth.service.spec.ts, test/jest.json |
Structure your explanation as:
- What it does — one sentence summary
- How it works — step-by-step with file:line references for each step
- Key design decisions — why it's built this way (patterns, trade-offs)
- How to extend it — what to change if someone wants to add to or modify this behaviour
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 · 26 lines · 0 tokens per session scan A dc51b6d5df18
explain 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 476 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.
build-fix
빌드 에러를 자동으로 분석하고 수정합니다.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.