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/gsd-installernpx skills add Softtor/nestjs-hexagonal --skill gsd-installergit 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/gsd-installer)<a href="https://agentmods.dev/skills/softtor/nestjs-hexagonal/gsd-installer"><img src="https://agentmods.dev/badge/skills/softtor/nestjs-hexagonal/gsd-installer.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.00094 | $0.01080 |
| Opus 5 | $0.00047 | $0.00540 |
| Sonnet 5 | $0.00019 | $0.00216 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade B, and why
gsd-installer scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
ls .claude-plugin/plugin.json 2>/dev/null || grep -r "nestjs-hexagonal" ~/.claude/plugins/ 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Installer for nestjs-hexagonal
Configures a NestJS project so that GSD workflows automatically leverage the nestjs-hexagonal plugin's skills and agents.
What This Does
- Adds a skill mapping section to the project's
CLAUDE.mdso GSD executor agents know which skills to invoke - Creates a GSD roadmap template with phases that map to plugin agents
- Optionally updates
.planning/PROJECT.mdif GSD is already initialized
Step 1: Detect Project State
Check what exists:
# GSD initialized?
ls .planning/PROJECT.md 2>/dev/null
# CLAUDE.md exists?
ls CLAUDE.md 2>/dev/null
# NestJS project?
ls nest-cli.json 2>/dev/null || ls apps/*/nest-cli.json 2>/dev/null
# Plugin installed?
ls .claude-plugin/plugin.json 2>/dev/null || grep -r "nestjs-hexagonal" ~/.claude/plugins/ 2>/dev/null
Step 2: Add Skill Mapping to CLAUDE.md
Append this section to the project's CLAUDE.md (create if not exists):
## NestJS Hexagonal Architecture (nestjs-hexagonal plugin)
### Skill Mapping for GSD Phases
When executing GSD phases that involve creating or modifying bounded contexts, use these skills and agents:
| Task | Skill / Agent | Model |
|------|---------------|-------|
| Domain modeling (entities, VOs, events) | `nestjs-hexagonal:domain-agent` | Opus 5 |
| Application layer (use cases, handlers) | `nestjs-hexagonal:application-agent` | Sonnet 5 |
| Infrastructure (repos, modules, adapters) | `nestjs-hexagonal:infrastructure-agent` | Sonnet 5 |
| Presentation (controllers, DTOs, Swagger) | `nestjs-hexagonal:presentation-agent` | Sonnet 5 |
| WebSocket broadcasting | `nestjs-hexagonal:broadcasting-agent` | Sonnet 5 |
| Architecture review | `nestjs-hexagonal:architecture-reviewer` | Opus 5 |
| Full BC scaffold | `nestjs-hexagonal:create-subdomain` | Orchestrator |
| Event chain debugging | `nestjs-hexagonal:event-debug-agent` | Opus 5 |
### Architecture Rules (enforced)
1. Entity extends `AggregateRoot` from `@nestjs/cqrs`
2. Repository is PURE persistence — no event dispatch
3. EventPublisher in Handler only, NEVER in UseCase
4. Module exports ONLY Port tokens
5. class-validator ONLY in presentation request DTOs
6. Write returns void or `{ id: string }`
### GSD Phase Template for Bounded Context
When creating a new bounded context via GSD, use this phase structure:
Phase X: <BC Name> Domain + Application
- Task 1: Domain modeling (dispatch domain-agent, Opus 5)
- Task 2: Application layer (dispatch application-agent, Sonnet 5)
Phase X+1: <BC Name> Infrastructure + Presentation
- Task 1: Infrastructure wiring (dispatch infrastructure-agent, Sonnet 5)
- Task 2: Presentation layer (dispatch presentation-agent, Sonnet 5)
- Task 3: Architecture review (dispatch architecture-reviewer, Opus 5)
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.
- 4d ago First seen · 115 lines · 94 tokens per session scan B 94ee0b1a7810
gsd-installer is a skill published in the GitHub repository Softtor/nestjs-hexagonal (5 stars, last pushed 24d ago), licensed MIT. It adds 94 tokens to every session and 1,080 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
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"…
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…