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 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/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/skills/softtor/nestjs-hexagonal/review-subdomain"><img src="https://agentmods.dev/badge/skills/softtor/nestjs-hexagonal/review-subdomain.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.00093 | $0.04495 |
| Opus 5.5 | $0.00037 | $0.01798 |
| Sonnet 5.5 | $0.00019 | $0.00899 |
| Haiku 4.5 | $0.00009 | $0.00449 |
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 21d 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 — 412 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). The rulebook decides everything it can decide; the agent reviews only the rest. Produce the structured report at the end.
The rubric in references/review-rubric.md lists the 35 checks; each one is marked with the rule id that covers it or with "residual (agent)".
Setup
Resolve the target directory from the argument. If no argument is given, ask the user for the path.
ls <bc-path>
If the directory does not exist, stop and report an error. Set BC_PATH to the resolved path relative to the project root (the CLI reports paths relative to the current directory). Locate the checker:
bunx nestjs-hexagonal-check --help >/dev/null 2>&1 && echo bunx || ls node_modules/.bin/nestjs-hexagonal-check
If neither works, the plugin is not installed in this project: skip steps 1 and 2, run the whole rubric by hand in step 3, and say in the report that the rulebook did not run.
Step 1 — Static rulebook (offline)
bunx nestjs-hexagonal-check --rulebook hexagonal --files '<BC_PATH>/**/*.ts' --classes static --format json > /tmp/review-static.json
- Drop
--rulebook hexagonalwhen the project has.claude/rulebook.yaml(the project rulebook is picked up by default;--project-rulebook <path>points at another file). The project rulebook adds its own rules and overrides and decides whethersofttor-conventions(tenant scoping, no emoji, English identifiers) applies. - Every finding carries
ruleId,severity(FAIL/WARN),path,line,evidenceandfix. Static FAILs are blocking and are reported verbatim; do not re-check them by hand. warningslists composition problems (a stale sha256 stamp marks the rununcalibrated; anexternalcheck without executor is skipped).
Step 2 — Semantic rulebook (Jev, one batch per file)
bunx nestjs-hexagonal-check --rulebook hexagonal --files '<BC_PATH>/**/*.ts' --classes semantic --format json > /tmp/review-semantic.json
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.
- 21d ago Changed · +4 lines 258ec8358ef8
- 1mo ago Changed e1878c4026fe
- 1mo ago Changed · +46 lines · +35 tokens per session c7e6e27e4cdb
- 2mo 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 21d ago), licensed MIT. It adds 93 tokens to every session and 4,495 once invoked, about $0.0004 per session on Opus 5.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
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
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-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…