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/proyecto26/projectx/nestjsnpx skills add proyecto26/projectx --skill nestjsgit clone --depth 1 https://github.com/proyecto26/projectxWrote 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/proyecto26/projectx/nestjs)<a href="https://agentmods.dev/skills/proyecto26/projectx/nestjs"><img src="https://agentmods.dev/badge/skills/proyecto26/projectx/nestjs.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.00037 | $0.01140 |
| Opus 5 | $0.00018 | $0.00570 |
| Sonnet 5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
nestjs 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 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.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NestJS Microservices Development
Project Structure
This project uses NestJS for three microservices:
apps/auth- Authentication (JWT, Passport)apps/order- Order management (integrates with Temporal)apps/product- Product catalog
Shared modules are in packages/core.
Creating a New Module
1. Create Module File
// feature/feature.module.ts
import { Module } from '@nestjs/common';
import { FeatureController } from './feature.controller';
import { FeatureService } from './feature.service';
@Module({
controllers: [FeatureController],
providers: [FeatureService],
exports: [FeatureService],
})
export class FeatureModule {}
2. Create Service with Repository Pattern
// feature/feature.service.ts
import { Injectable } from '@nestjs/common';
import { PrismaService } from '@projectx/db';
@Injectable()
export class FeatureService {
constructor(private readonly prisma: PrismaService) {}
async findAll() {
return this.prisma.feature.findMany();
}
async findOne(id: string) {
return this.prisma.feature.findUnique({ where: { id } });
}
async create(data: CreateFeatureDto) {
return this.prisma.feature.create({ data });
}
}
3. Create Controller with Swagger
// feature/feature.controller.ts
import { Controller, Get, Post, Body, Param } from '@nestjs/common';
import { ApiTags, ApiOperation, ApiResponse } from '@nestjs/swagger';
import { FeatureService } from './feature.service';
@ApiTags('features')
@Controller('features')
export class FeatureController {
constructor(private readonly featureService: FeatureService) {}
@Get()
@ApiOperation({ summary: 'Get all features' })
@ApiResponse({ status: 200, description: 'Returns all features' })
findAll() {
return this.featureService.findAll();
}
@Get(':id')
@ApiOperation({ summary: 'Get feature by ID' })
findOne(@Param('id') id: string) {
return this.featureService.findOne(id);
}
@Post()
@ApiOperation({ summary: 'Create a feature' })
create(@Body() createFeatureDto: CreateFeatureDto) {
return this.featureService.create(createFeatureDto);
}
}
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 · 203 lines · 37 tokens per session scan A bf3acb06ea0b
nestjs is a skill published in the GitHub repository proyecto26/projectx (83 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,140 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-30.
Other skills, from other repositories
hono-rpc
Hono RPC - end-to-end type-safe API client generation with hc client and TypeScript inference.
nifra
Use when writing, reviewing, or debugging code in a Nifra project (@nifrajs/ packages, nifra CLI, server()/defineContract, loaders and actions, file routes under routes/). Explains how to reach Nifra's live MCP tools so signatures come from the installed version instead of memory, and which sibling skill to load for…
fullstack-typescript-monorepo
Apply a TypeScript monorepo preset for fullstack systems with shared contracts, frontend and backend package boundaries, CI caching, and consistent developer workflows.
hono-rpc
Hono RPC - end-to-end type-safe API client generation with hc client and TypeScript inference.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
typescript-providers
Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, and Claude Agent SDK. Use for provider-specific TS work; do not use for core-only changes.