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 skills add DauQuangThanh/hanoi-rainbow --skill backend-codinggit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/backend-coding)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/backend-coding"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/backend-coding/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/backend-coding"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/backend-coding.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00095 | $0.02659 |
| Opus 5 | $0.00048 | $0.01329 |
| Sonnet 5 | $0.00019 | $0.00532 |
| Haiku 4.5 | $0.00010 | $0.00266 |
Grade A, and why
backend-coding 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 8d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Coding
Build production-ready backend services with proper architecture, security, performance optimization, and testing.
Core Development Workflow
Follow this systematic approach for backend implementation:
1. Design API Endpoints
Define clear, RESTful API contracts before implementation.
REST API Design Pattern:
Resource-based URLs (use plural nouns):
✅ GET /api/v1/users - List users (paginated)
✅ GET /api/v1/users/:id - Get user by ID
✅ POST /api/v1/users - Create new user
✅ PUT /api/v1/users/:id - Replace entire user
✅ PATCH /api/v1/users/:id - Update user fields
✅ DELETE /api/v1/users/:id - Delete user
❌ Avoid verb-based URLs:
❌ /api/v1/getUsers
❌ /api/v1/createUser
Basic Example (Express.js):
router.get('/users',
query('page').optional().isInt({ min: 1 }).toInt(),
query('limit').optional().isInt({ min: 1, max: 100 }).toInt(),
async (req, res, next) => {
try {
const errors = validationResult(req);
if (!errors.isEmpty()) {
return res.status(400).json({ errors: errors.array() });
}
const page = req.query.page as number || 1;
const limit = req.query.limit as number || 20;
const offset = (page - 1) * limit;
const { users, total } = await userService.findAll({
limit, offset
});
res.json({
data: users,
pagination: { page, limit, total }
});
} catch (error) {
next(error);
}
}
);
For complete patterns: api-design.md
2. Implement Database Layer
Use repository pattern for clean separation and testability.
Repository Pattern (TypeORM):
export class UserRepository {
private repository: Repository<User>;
async findAll(params: { search?: string; limit: number; offset: number }) {
const queryBuilder = this.repository
.createQueryBuilder('user')
.orderBy('user.createdAt', 'DESC');
if (params.search) {
queryBuilder.where(
'user.name ILIKE :search OR user.email ILIKE :search',
{ search: `%${params.search}%` }
);
}
return queryBuilder
.take(params.limit)
.skip(params.offset)
.getManyAndCount();
}
async create(userData: UserCreate): Promise<User> {
const hashedPassword = await bcrypt.hash(userData.password, 12);
const user = this.repository.create({
...userData,
password: hashedPassword
});
return this.repository.save(user);
}
}
What ships with it
7 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.
- 8d ago First seen · 401 lines · 95 tokens per session scan A e607331edce9
backend-coding is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 95 tokens to every session and 2,659 once invoked, about $0.0005 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
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-driven-development
Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.
dotnet-forge
Generate production-ready .NET Core APIs with Entity Framework, repository pattern, CQRS, and enterprise standards.
nestjs-forge
Generate production-ready NestJS + TypeORM APIs with modules, guards, interceptors, and enterprise standards.
spring-forge
Generate production-ready Spring Boot + JPA APIs with layered architecture, MapStruct, Jakarta validation, and audit trails.