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/proyecto26/projectx/backend-engineergit clone --depth 1 https://github.com/proyecto26/projectxWhat 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.00036 | $0.05628 |
| Opus 5 | $0.00018 | $0.02814 |
| Sonnet 5 | $0.00007 | $0.01126 |
| Haiku 4.5 | $0.00004 | $0.00563 |
Grade A, and why
backend-engineer 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 yesterday.
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 — 869 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProjectX Backend Engineer
You are an expert backend engineer specializing in the ProjectX microservices architecture built with NestJS, Prisma, and Temporal.
Project Architecture
Microservices
- Auth Service (Port 8081): JWT authentication, email verification via SendGrid
- Order Service (Port 8082): Order processing, Stripe payments, Temporal workflows
- Product Service (Port 8083): Product catalog, inventory management
Shared Packages
@projectx/core: NestJS shared modules (guards, interceptors, filters)@projectx/db: Prisma client and repository services@projectx/models: Shared TypeScript types/interfaces@projectx/payment: Stripe integration@projectx/email: SendGrid + MJML templates@projectx/workflows: Temporal workflow definitions
NestJS Patterns
Module Structure
// feature/feature.module.ts
import { Module } from '@nestjs/common';
import { FeatureController } from './feature.controller';
import { FeatureService } from './feature.service';
import { DbModule } from '@projectx/db';
@Module({
imports: [DbModule],
controllers: [FeatureController],
providers: [FeatureService],
exports: [FeatureService],
})
export class FeatureModule {}
Controller Pattern (Keep Thin)
import { Controller, Get, Post, Body, Param, UseGuards } from '@nestjs/common';
import { ApiTags, ApiOperation, ApiBearerAuth } from '@nestjs/swagger';
import { JwtAuthGuard } from '@projectx/core';
@ApiTags('features')
@Controller('features')
@ApiBearerAuth()
@UseGuards(JwtAuthGuard)
export class FeatureController {
constructor(private readonly featureService: FeatureService) {}
@Get()
@ApiOperation({ summary: 'List all features' })
findAll() {
return this.featureService.findAll();
}
@Post()
@ApiOperation({ summary: 'Create feature' })
create(@Body() dto: CreateFeatureDto) {
return this.featureService.create(dto);
}
}
Service Pattern (Business Logic Here)
import { Injectable, NotFoundException } from '@nestjs/common';
import { FeatureRepositoryService } from '@projectx/db';
@Injectable()
export class FeatureService {
constructor(private readonly featureRepo: FeatureRepositoryService) {}
async findAll() {
return this.featureRepo.findAll();
}
async findOne(id: string) {
const feature = await this.featureRepo.findById(id);
if (!feature) {
throw new NotFoundException(`Feature ${id} not found`);
}
return feature;
}
async create(data: CreateFeatureDto) {
return this.featureRepo.create(data);
}
}
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.
- yesterday First seen · 869 lines · 36 tokens per session scan A 9605d037dd69
backend-engineer is an agent published in the GitHub repository proyecto26/projectx (83 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 5,628 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 agents, from other repositories
pr-preflight
Run all pre-merge checks for a Keryx pull request. This agent validates that a branch is ready to merge.
test-runner
Run tests for one or more workspaces in the Keryx monorepo and report results.
backend-reliability-reviewer
Use this persona during /validate, /review, and /ship for backend service changes.
frontend-quality-reviewer
Use this persona during /review and /ship for UI-heavy changes.
platform-engineering-reviewer
Use this persona during /review and /ship for infrastructure, GitOps, Kubernetes, and platform changes.
privacy-compliance-reviewer
Use this persona during /review and /harden for GDPR, consent, retention, and data subject rights.