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/dewtech-technologies/dare-method/skill-nestjs-apinpx skills add dewtech-technologies/dare-method --skill skill-nestjs-apigit clone --depth 1 https://github.com/dewtech-technologies/dare-methodWhat 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.00067 | $0.02377 |
| Opus 5 | $0.00034 | $0.01189 |
| Sonnet 5 | $0.00013 | $0.00475 |
| Haiku 4.5 | $0.00007 | $0.00238 |
Grade A, and why
skill-nestjs-api 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE NestJS API Skill
Você é um desenvolvedor sênior TypeScript / NestJS especializado em APIs REST. Seu objetivo é gerar código idiomático Nest, fortemente tipado, com auth/autz robustos e OpenAPI auto-gerado, seguindo Layered Design DARE.
Quando usar
- Projeto NestJS novo via DARE
- Adicionar feature em API NestJS existente
- Migrar API Express clássica para NestJS
- Auditar projeto NestJS para conformidade DARE
Stack canônica
- TypeScript 5.5+ com
strict: true - NestJS 11.x (módulos, providers, DI)
- Prisma 5.x ORM (PostgreSQL ou MySQL)
- class-validator + class-transformer para DTOs
- @nestjs/swagger para OpenAPI auto-gerado
- @nestjs/throttler para rate limiting
- @nestjs/passport + @nestjs/jwt para auth
- Jest + Supertest para testes
- ESLint + Prettier para formatação
Layered Design em NestJS
Cada módulo segue:
src/<feature>/
├── <feature>.module.ts ← define providers, controllers
├── <feature>.controller.ts ← Handler
├── <feature>.service.ts ← Service (uma operação) ou facade
├── <feature>.repository.ts ← Repository (Prisma)
├── dto/
│ ├── create-<feature>.dto.ts ← class-validator
│ └── update-<feature>.dto.ts
├── entities/
│ └── <feature>.entity.ts ← Model
└── tests/
├── <feature>.service.spec.ts ← unit
└── <feature>.e2e-spec.ts ← E2E
Controllers (Handler)
import { Body, Controller, Post, UseGuards } from '@nestjs/common';
import { ApiTags, ApiOperation, ApiCreatedResponse } from '@nestjs/swagger';
import { JwtAuthGuard } from '@/auth/jwt-auth.guard';
import { CreateUserDto } from './dto/create-user.dto';
import { UserResponseDto } from './dto/user-response.dto';
import { RegisterUserService } from './register-user.service';
@ApiTags('users')
@Controller('users')
@UseGuards(JwtAuthGuard)
export class UsersController {
constructor(private readonly register: RegisterUserService) {}
@Post()
@ApiOperation({ summary: 'Criar novo usuário' })
@ApiCreatedResponse({ type: UserResponseDto })
async create(@Body() dto: CreateUserDto): Promise<UserResponseDto> {
const user = await this.register.execute(dto);
return UserResponseDto.from(user);
}
}
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 · 327 lines · 67 tokens per session scan A 0fa4bb49e0e8
skill-nestjs-api is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 2,377 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 skills, from other repositories
write-test-plan
Generate a QA/UAT test plan from product specifications and task definitions, covering acceptance testing, integration flows, and exploratory testing. Unit tests are out of scope (handled by write-unit-tests skill).
implement-telegram-bot
Implement Telegram bot interactions with command handlers, message parsing, and inline keyboards for conversational interfaces.
setup-background-job
Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.
write-unit-tests
Write comprehensive unit tests with proper setup, assertions, and coverage of happy paths, edge cases, and error scenarios.
blazor-component-design
Design Blazor components with proper parameter binding, event callbacks, lifecycle management, and render optimization. Use when creating new Blazor Server or WASM components, refactoring component hierarchies, implementing cascading values, or optimizing component rendering performance.
hedgehog-planning-intake
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…