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/hamzaali81/nestjs-agent-workflow-kit/code-reviewnpx skills add hamzaali81/nestjs-agent-workflow-kit --skill code-reviewgit clone --depth 1 https://github.com/hamzaali81/nestjs-agent-workflow-kitWrote 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/hamzaali81/nestjs-agent-workflow-kit/code-review)<a href="https://agentmods.dev/skills/hamzaali81/nestjs-agent-workflow-kit/code-review"><img src="https://agentmods.dev/badge/skills/hamzaali81/nestjs-agent-workflow-kit/code-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 | $0.00054 | $0.01561 |
| Opus 5 | $0.00027 | $0.00781 |
| Sonnet 5 | $0.00011 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
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 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Review changed files against docs/standards and relevant .agents/skills references. Do not duplicate full convention text in the report; cite the relevant standard or skill section instead.
Review Steps
- Scope: Identify changed files with the relevant diff scope (
git diff --name-only,--cached, orHEAD~N). - Classify: Group changed files by type: controller (
*.controller.ts), service (*.service.ts), module (*.module.ts), DTO (dto/*.ts), repository (*.repository.ts), Prisma schema/migration, cross-cutting (common/**filters/guards/interceptors/pipes), config (config/**), and test (*.spec.ts,*.e2e-spec.ts). - Read the real code: For each changed controller, read the full handler bodies (not just the diff) to judge whether logic/data access leaked in. For services, read the methods touched. Do not rely only on
git diff --stat. - Conventions: Apply every applicable standard in the checklist below, including each standard's audit/check guidance.
- Report: List deviations in one flat list. If there are no deviations, say so explicitly.
Routing Hints
Use this table to know where to look first. It does not replace the mandatory coverage checklist.
| Changed files | Read |
|---|---|
| Cross-cutting / unfamiliar area | architecture.md first, then topic files below |
| Any TS | core-engineering.md |
*.controller.ts |
controllers.md, dtos-and-validation.md, error-handling.md |
dto/*.ts |
dtos-and-validation.md, openapi-swagger skill |
*.service.ts |
providers-and-services.md |
*.module.ts |
modules.md |
*.repository.ts, schema.prisma |
database.md, prisma-data-layer skill |
common/** (filter/guard/etc.) |
error-handling.md |
config/** |
configuration.md |
*.spec.ts, *.e2e-spec.ts |
testing.md |
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 · 101 lines · 54 tokens per session scan A b0a3b88baa90
code-review is a skill published in the GitHub repository hamzaali81/nestjs-agent-workflow-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,561 once invoked, about $0.0003 per session on Opus 5. 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 encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…