imlazy-backend

imlazy-backend is a skill for Claude Code from hnikoloski/imlazy. It costs 32 tokens per session (3,183 once invoked), scanned A, a copy of backend-patterns, MIT.

Guidance for building server-side applications with Node.js, Express, and Next.js API routes. It covers application structure, APIs, database access, caching, background work, validation, and middleware.

In plain words
What is it for?
Use it when designing APIs, organizing repository, service, and controller layers, improving database queries, adding caching or background jobs, and implementing authentication, logging, validation, or rate limiting.
Why use it?
It helps avoid common backend problems such as repeated database queries, unclear responsibilities, weak error handling, and poorly structured server code.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the imlazy plugin — 26 skills, 1 command, 1 hook shipped together

Good fit Use it when designing APIs, organizing repository, service, and controller layers, improving database queries, adding caching or background jobs, and implementing authentication, logging, validation, or rate limiting.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hnikoloski/imlazy/imlazy-backend
Install

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.

Any agent
npx skills add hnikoloski/imlazy --skill imlazy-backend
Clone the repo
git clone --depth 1 https://github.com/hnikoloski/imlazy

Made for: Claude Code.

Or install imlazy, the plugin that ships this one along with the rest of its 26 skills, 1 command, 1 hook.

Wrote 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.

agentmods badge for imlazy-backend

README.md
[![agentmods](https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-backend/github.svg)](https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-backend)
Your own site
<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-backend"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-backend/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.

agentmods 80×15 button for imlazy-backend

Your own site · 80×15
<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-backend"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-backend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,183 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.03183
Opus 5 $0.00016 $0.01591
Sonnet 5 $0.00006 $0.00637
Haiku 4.5 $0.00003 $0.00318

Measured 11d ago against content hash 2eb91a16c329, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

imlazy-backend 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 11d 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.

Origin

This is a copy

88% identical to backend-patterns — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/imlazy-backend/SKILL.md · 561 lines

How it starts

The opening of the file, as written. The whole thing — 561 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Backend Development Patterns

Backend architecture patterns and best practices for scalable server-side applications.

When to Activate

  • Designing REST or GraphQL API endpoints
  • Implementing repository, service, or controller layers
  • Optimizing database queries (N+1, indexing, connection pooling)
  • Adding caching (Redis, in-memory, HTTP cache headers)
  • Setting up background jobs or async processing
  • Structuring error handling and validation for APIs
  • Building middleware (auth, logging, rate limiting)

API Design Patterns

RESTful API Structure

// PASS: Resource-based URLs
GET    /api/markets                 # List resources
GET    /api/markets/:id             # Get single resource
POST   /api/markets                 # Create resource
PUT    /api/markets/:id             # Replace resource
PATCH  /api/markets/:id             # Update resource
DELETE /api/markets/:id             # Delete resource

// PASS: Query parameters for filtering, sorting, pagination
GET /api/markets?status=active&sort=volume&limit=20&offset=0

Repository Pattern

// Abstract data access logic
interface MarketRepository {
  findAll(filters?: MarketFilters): Promise<Market[]>
  findById(id: string): Promise<Market | null>
  create(data: CreateMarketDto): Promise<Market>
  update(id: string, data: UpdateMarketDto): Promise<Market>
  delete(id: string): Promise<void>
}

class SupabaseMarketRepository implements MarketRepository {
  async findAll(filters?: MarketFilters): Promise<Market[]> {
    let query = supabase.from('markets').select('*')

    if (filters?.status) {
      query = query.eq('status', filters.status)
    }

    if (filters?.limit) {
      query = query.limit(filters.limit)
    }

    const { data, error } = await query

    if (error) throw new Error(error.message)
    return data
  }

  // Other methods...
}

Service Layer Pattern

// Business logic separated from data access
class MarketService {
  constructor(private marketRepo: MarketRepository) {}

  async searchMarkets(query: string, limit: number = 10): Promise<Market[]> {
    // Business logic
    const embedding = await generateEmbedding(query)
    const results = await this.vectorSearch(embedding, limit)

    // Fetch full data
    const markets = await this.marketRepo.findByIds(results.map(r => r.id))

    // Sort by similarity
    return markets.sort((a, b) => {
      const scoreA = results.find(r => r.id === a.id)?.score || 0
      const scoreB = results.find(r => r.id === b.id)?.score || 0
      return scoreA - scoreB
    })
  }

  private async vectorSearch(embedding: number[], limit: number) {
    // Vector search implementation
  }
}

Read the full file on GitHub · 561 lines

Changes

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.

  1. 11d ago First seen · 561 lines · 32 tokens per session scan A 2eb91a16c329

Subscribe to this mod's changes

imlazy-backend is a skill published in the GitHub repository hnikoloski/imlazy (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 3,183 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to backend-patterns, differing in 55 lines, and is treated as a copy.