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/softtor/nestjs-hexagonal/review-subdomainnpx skills add Softtor/nestjs-hexagonal --skill review-subdomaingit clone --depth 1 https://github.com/Softtor/nestjs-hexagonalWrote 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/softtor/nestjs-hexagonal/review-subdomain)<a href="https://agentmods.dev/skills/softtor/nestjs-hexagonal/review-subdomain"><img src="https://agentmods.dev/badge/skills/softtor/nestjs-hexagonal/review-subdomain.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.00058 | $0.03137 |
| Opus 5 | $0.00029 | $0.01569 |
| Sonnet 5 | $0.00012 | $0.00627 |
| Haiku 4.5 | $0.00006 | $0.00314 |
Grade A, and why
review-subdomain 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 6d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-subdomain
Review a bounded context for architectural compliance. Accept the BC path as the argument (e.g., src/enterprise/billing/invoices). Run each dimension in order. Produce a structured report at the end.
The rubric with scoring criteria is in references/review-rubric.md.
Setup
Resolve the target directory from the argument. If no argument is given, ask the user for the path.
Verify the directory exists:
ls <bc-path>
If the directory does not exist, stop and report an error.
Set BC_PATH to the resolved absolute path. All grep and glob searches below use BC_PATH as the root.
Dimension 1 — Domain Purity
Purpose: Confirm the domain layer has zero framework or infrastructure dependencies.
Run the following checks against <BC_PATH>/domain/:
Check D1 — No NestJS common imports in domain:
grep -r "@nestjs/common" <BC_PATH>/domain/ --include="*.ts" -l
FAIL if any files are returned. Exception: @nestjs/cqrs is allowed (for AggregateRoot, IEvent).
Check D2 — No class-validator in VOs:
grep -r "class-validator" <BC_PATH>/domain/value-objects/ --include="*.ts" -l
FAIL if any files are returned. class-validator is allowed in domain/validators/ only.
Check D3 — No Prisma imports in domain:
grep -r "PrismaClient\|PrismaService\|@prisma/client" <BC_PATH>/domain/ --include="*.ts" -l
FAIL if any files are returned.
Check D4 — Entity uses apply() not addDomainEvent():
grep -r "addDomainEvent\|pullDomainEvents" <BC_PATH>/domain/ --include="*.ts" -l
FAIL if any files are returned. Entities must use this.apply(event).
Check D5 — Entity has create() and restore() factories:
For each entity file found in <BC_PATH>/domain/entities/:
- Read the file
- Confirm
static create(is present - Confirm
static restore(is present - Confirm
private constructoris present
FAIL if any entity is missing one of these.
Check D6 — Repository interface is a pure interface (no @Injectable):
grep -r "@Injectable" <BC_PATH>/domain/repositories/ --include="*.ts" -l
FAIL if any files are returned.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 362 lines · 58 tokens per session scan A 496961afff35
review-subdomain is a skill published in the GitHub repository Softtor/nestjs-hexagonal (5 stars, last pushed 26d ago), licensed MIT. It adds 58 tokens to every session and 3,137 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
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-debt
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what…
brooks-health
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all…
brooks-review
PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues…
architecture-compass
Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use…