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 onboard-projectgit 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/onboard-project)<a href="https://agentmods.dev/skills/softtor/nestjs-hexagonal/onboard-project"><img src="https://agentmods.dev/badge/skills/softtor/nestjs-hexagonal/onboard-project/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/onboard-project"><img src="https://agentmods.dev/badge/skills/softtor/nestjs-hexagonal/onboard-project.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.00113 | $0.01518 |
| Opus 5.5 | $0.00045 | $0.00607 |
| Sonnet 5.5 | $0.00023 | $0.00304 |
| Haiku 4.5 | $0.00011 | $0.00152 |
Grade A, and why
onboard-project 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
onboard-project
Executable checklist for a project that wants the rulebook enforced. The plugin is inert until step 2 exists: the hooks fire only for a project with .claude/rulebook.yaml (or NESTJS_HEXAGONAL_RULEBOOK pointing at a file), and the CLI is a plain dev dependency. README section "Onboarding another project" is the prose version of this list.
Resolve the package runner first ("Package runner" in nestjs-hexagonal:using-nestjs-hexagonal); the commands below use bun, replace with the project's runner.
1. Decide which rulebooks apply
| Rulebook | Extend it when |
|---|---|
hexagonal |
always: project-agnostic hexagonal + DDD + CQRS rules (hex/*) |
softtor-conventions |
the project is multi-tenant with an organizationId scope on every query, bans emoji in code and requires English identifiers (softtor/*); a project that does not share those conventions must not extend it |
Ask the user when the answer is not obvious from the codebase (grep for organizationId in repositories).
2. Create .claude/rulebook.yaml with stamps
Print the extends block from the installed plugin; the sha256 pins the content of each base rulebook the project is calibrated against:
bunx nestjs-hexagonal-check stamp hexagonal # add softtor-conventions when it applies
Write the file (the example is rulebooks/project.example.rulebook.yaml in the plugin):
$schema: nestjs-hexagonal/rulebook@1
id: <project-id> # lowercase, becomes the namespace of the project's own rules
version: 0.1.0
extends:
- id: hexagonal
version: 1.4.0
sha256: <from the stamp command>
model:
provider: typesafe
pin: jev-1.13.0
rules: [] # project rules under <project-id>/<slug>, static first
overrides: [] # by id: disabled, severity, scope, thresholds, check.unlessInEnclosingDeclaration (regex rules)
A stale stamp never blocks: the CLI reports rulebook-mismatch and marks the run uncalibrated. Refresh the stamps when the plugin is updated (stamp again).
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 5d216d7e3ff4
- 1mo ago First seen · 100 lines · 113 tokens per session scan A 2876c3775732
onboard-project is a skill published in the GitHub repository Softtor/nestjs-hexagonal (5 stars, last pushed 21d ago), licensed MIT. It adds 113 tokens to every session and 1,518 once invoked, about $0.0005 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-09-21.
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…