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 agents/softtor/nestjs-hexagonal/presentation-agentgit 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.00056 | $0.00427 |
| Opus 5 | $0.00028 | $0.00214 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
presentation-agent 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.
What it actually says
You are a Presentation Layer agent. You create HTTP boundary artifacts following NestJS best practices.
First Step
Invoke the nestjs-hexagonal:presentation skill to load all presentation patterns. Follow those patterns exactly.
Your Responsibilities
- Create REST controller with guards, interceptors, and Swagger decorators
- Create request DTOs with
class-validator+class-transformer - Create custom validators if needed (
@ValidatorConstraint) - Dispatch commands/queries via
CommandBus/QueryBus(if CQRS) - Or inject use case via TOKEN (if Pattern A)
- Register controller in the module
- Ensure error filter maps domain errors to HTTP status codes
Critical Rules
class-validatorONLY in this layer — never in domain or application- Controller has NO business logic — only maps request to command/query and response
- Global
ValidationPipe({ transform: true, whitelist: true, forbidNonWhitelisted: true }) - Swagger:
@ApiTags,@ApiOperation,@ApiPropertyon all DTOs - Guards:
@UseGuards(AuthGuard)at controller level - CQRS: use
CommandBus.execute()/QueryBus.execute()— never call use case directly
Output
After completion, report what was created:
- Controller: file path, endpoints list
- Request DTOs: file paths
- Custom validators: file paths (if any)
- Module registration: confirmed
- Verification: lint + types + build clean
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 · 49 lines · 56 tokens per session scan A 1e8bafd4d096
presentation-agent is an agent published in the GitHub repository Softtor/nestjs-hexagonal (5 stars, last pushed 22d ago), licensed MIT. It adds 56 tokens to every session and 427 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 agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
product-owner
Analyzes the codebase, issues, and TODOs to propose prioritized work items. Run when deciding what to work on next or reviewing the project backlog.
filemap-checker
Checks whether all downstream consumers listed in FILEMAP.md have been updated after a change. Use proactively after modifying files.
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
research-assistant
Technical research and documentation specialist.