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.
git 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/debug)<a href="https://agentmods.dev/commands/hmake98/nestjs-starter/debug"><img src="https://agentmods.dev/badge/commands/hmake98/nestjs-starter/debug/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/commands/hmake98/nestjs-starter/debug"><img src="https://agentmods.dev/badge/commands/hmake98/nestjs-starter/debug.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.00710 |
| Opus 5.5 | $0.00000 | $0.00284 |
| Sonnet 5.5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
debug 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 1mo 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug the following issue in this NestJS project: $ARGUMENTS
Read the relevant files and diagnose the root cause. Use the knowledge below to guide your investigation.
Common issues and where to look
Dependency Injection / Module errors
UnknownExportException — a provider is in exports but not in providers of the same module.
UnknownDependenciesException — a provider's dependency is not in scope. Check:
- Is the dependency's module imported?
- Is the dependency in that module's
providers? - Is that module in
exportsso it's visible here?
Key rule in this repo: AuthModule and UserModule both import DatabaseModule directly. Feature modules never import each other. Read src/modules/auth/auth.module.ts and src/modules/user/user.module.ts.
Prisma / database errors
PrismaClientInitializationError — DATABASE_URL not set or unreachable. In Docker, the URL must point to the postgres service name, not localhost.
PrismaConfigEnvError — DATABASE_URL not set at build time. prisma generate uses prisma/prisma.config.ts which reads process.env.DATABASE_URL (no throw on undefined — safe at build time).
Migration not applied — run npm run db:migrate-prod or check docker-entrypoint.sh ran successfully.
Docker / container errors
Cannot find module '...' — npm prune --omit=dev removed a package that should be in dependencies not devDependencies. Check package.json.
App binding to 127.0.0.1 — HTTP_HOST must be 0.0.0.0 in Docker. Set in docker-compose.yml environment block.
Stale dist/ — volume mount .:/app overwrites the built dist. The docker-compose.yml in this repo uses the dev stage with nest start --watch, not a pre-built dist.
JWT / Auth errors
401 Unauthorized on a protected route — check the Authorization: Bearer <token> header is present and the token is not expired.
401 on a public route — check @PublicRoute() decorator is applied. Read src/common/request/guards/jwt-access.guard.ts to see how it checks the metadata.
403 Forbidden — RolesGuard blocked the request. Check @AllowedRoles on the route matches the user's role field.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A c1a89ebcc954
debug is a command published in the GitHub repository hmake98/nestjs-starter (64 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 710 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
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
web-scene-audit
Audit web game scenes, screen flow, state transitions, and teardown patterns.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.