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/presentationnpx skills add Softtor/nestjs-hexagonal --skill presentationgit clone --depth 1 https://github.com/Softtor/nestjs-hexagonalWhat 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.00049 | $0.02454 |
| Opus 5 | $0.00024 | $0.01227 |
| Sonnet 5 | $0.00010 | $0.00491 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
presentation 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 2d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Layer
The presentation layer is the HTTP boundary. It owns input validation, Swagger docs, and error mapping. It must not contain business logic.
Directory Structure
infrastructure/
└── controllers/
├── <context>.controller.ts
├── __tests__/
│ └── <context>.controller.spec.ts
└── dtos/
├── create-<context>.request.dto.ts
├── update-<context>.request.dto.ts
├── list-<context>.request.dto.ts
└── __tests__/
└── create-<context>.request.dto.spec.ts
Or as a top-level presentation/ folder when separated from infrastructure/:
presentation/
├── controllers/
│ └── <context>.controller.ts
├── dtos/
│ └── create-<context>.http-dto.ts
├── presenters/
│ └── create-<context>.presenter.ts # maps use case output to HTTP response
└── validators/
└── <field>.validator.ts # @ValidatorConstraint classes
1. Controller Pattern
Use CommandBus / QueryBus for CQRS contexts. Use @Inject(TOKEN) for plain use case contexts.
// controllers/<context>.controller.ts
import {
Controller, Post, Get, Patch, Delete, Body, Param, Query,
HttpCode, HttpStatus, UseGuards,
} from '@nestjs/common';
import { CommandBus, QueryBus } from '@nestjs/cqrs';
import {
ApiTags, ApiBearerAuth, ApiOperation, ApiResponse, ApiBody,
} from '@nestjs/swagger';
import { AuthGuard } from '@/auth/guards/auth.guard';
import { CurrentUser, User } from '@/auth/decorators/current-user.decorator';
import { CurrentOrganization, OrgContext } from '@/auth/decorators/current-organization.decorator';
import { Create<Context>RequestDto } from './dtos/create-<context>.request.dto';
import { Create<Context>Command } from '../../application/commands/create-<context>.command';
import { Get<Context>Query } from '../../application/queries/get-<context>.query';
import { List<Context>Query } from '../../application/queries/list-<context>.query';
@ApiTags('<Contexts>')
@Controller('<contexts>')
@UseGuards(AuthGuard)
@ApiBearerAuth()
export class <Context>Controller {
constructor(
private readonly commandBus: CommandBus,
private readonly queryBus: QueryBus,
) {}
@Post()
@HttpCode(HttpStatus.CREATED)
@ApiOperation({ summary: 'Create a new <context>' })
@ApiResponse({ status: 201, description: '<Context> created' })
@ApiResponse({ status: 400, description: 'Validation error' })
@ApiResponse({ status: 401, description: 'Unauthorized' })
async create(
@Body() dto: Create<Context>RequestDto,
@CurrentOrganization() org: OrgContext,
): Promise<{ id: string }> {
return this.commandBus.execute(
new Create<Context>Command(org.id, dto.name),
);
}
@Get(':id')
@ApiOperation({ summary: 'Get <context> by id' })
@ApiResponse({ status: 200, description: '<Context> found' })
@ApiResponse({ status: 404, description: '<Context> not found' })
async findOne(
@Param('id') id: string,
@CurrentOrganization() org: OrgContext,
) {
return this.queryBus.execute(new Get<Context>Query(id, org.id));
}
@Get()
@ApiOperation({ summary: 'List <contexts> with pagination' })
async findAll(
@Query() query: List<Context>RequestDto,
@CurrentOrganization() org: OrgContext,
) {
return this.queryBus.execute(
new List<Context>Query({ organizationId: org.id, ...query }),
);
}
@Delete(':id')
@HttpCode(HttpStatus.NO_CONTENT)
@ApiOperation({ summary: 'Delete a <context>' })
@ApiResponse({ status: 204, description: 'Deleted' })
async remove(
@Param('id') id: string,
@CurrentOrganization() org: OrgContext,
): Promise<void> {
await this.commandBus.execute(new Delete<Context>Command(id, org.id));
}
}
What ships with it
4 files 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.
- 2d ago First seen · 306 lines · 49 tokens per session scan A a221e6d3b1d0
presentation is a skill published in the GitHub repository Softtor/nestjs-hexagonal (5 stars, last pushed 22d ago), licensed MIT. It adds 49 tokens to every session and 2,454 once invoked, about $0.0002 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
design-patterns
Full-spectrum Design Patterns skill: Detect anti-patterns in existing codebases, diagnose architectural debt, propose optimal patterns (GoF, SOLID, DDD, CQRS, Microservices, Cloud), and generate production-ready boilerplate code. Optimized for Next.js, FastAPI, NestJS, Django, Express, and Go.
clean-architecture
Implement Clean Architecture combined with CQRS for scalable NestJS applications.
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-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-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.