backend

backend is a skill for Claude Code, Codex from wewpellex21/code-sensei. It costs 34 tokens per session (673 once invoked), scanned A, a copy of backend, MIT.

Backend development builds the server-side part of an application: the code that stores data, processes requests, handles logins, and talks to databases. It includes servers and API routes, which are the addresses that handle specific requests.

In plain words
What is it for?
Use it when creating servers, API routes, or backend code with Express, Fastify, or Next.js. It also covers common request actions such as reading, creating, updating, and deleting data.
Why use it?
It helps create the code that runs outside the user's browser and handles the application's core work. It provides guidance when building server code or API handlers.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when creating servers, API routes, or backend code with Express, Fastify, or Next.js. It also covers common request actions such as reading, creating, updating, and deleting data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wewpellex21/code-sensei/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 wewpellex21/code-sensei --skill backend
Clone the repo
git clone --depth 1 https://github.com/wewpellex21/code-sensei

Made for: Claude Code, Codex.

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 backend

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/wewpellex21/code-sensei/backend"><img src="https://agentmods.dev/badge/skills/wewpellex21/code-sensei/backend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 673 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 100% 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.00034 $0.00673
Opus 5.5 $0.00014 $0.00269
Sonnet 5.5 $0.00007 $0.00135
Haiku 4.5 $0.00003 $0.00067

Measured 1mo ago against content hash ff33cc8031a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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

100% identical to backend — 0 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/backend/SKILL.md · 55 lines

How it starts

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

Backend Development — CodeSensei Teaching Module

What is a Backend?

  • Analogy: If your website is a restaurant, the frontend is the dining room (what customers see) and the backend is the kitchen (where the real work happens). The backend stores data, processes requests, handles logins, and talks to databases.
  • Key insight: The backend runs on a SERVER (a computer somewhere in the cloud), not in the user's browser.

Servers

  • Analogy: A server is like a receptionist. It sits there waiting for requests ("I want to see the homepage" or "save this form data"), then responds appropriately.
  • Express.js is the most common server framework in vibecoded projects. It's like a template for building that receptionist — you tell it "when someone asks for X, do Y."

Routes / Endpoints

  • Analogy: Routes are like departments in a company. /api/users is the Users department. /api/products is Products. Each one handles specific requests.
  • HTTP Methods (the verbs):
    • GET — "Give me data" (reading)
    • POST — "Here's new data, save it" (creating)
    • PUT/PATCH — "Update this existing data" (editing)
    • DELETE — "Remove this data" (deleting)
  • Quiz: "If someone fills out a signup form, which HTTP method sends their data to the server?"

APIs (Application Programming Interfaces)

  • Analogy: An API is a menu at a restaurant. It lists what you can order (available requests), what you need to provide (required data), and what you'll get back (the response). You don't need to know HOW the kitchen cooks it — you just order from the menu.
  • REST API — the most common style. Uses URLs as addresses and HTTP methods as actions.
  • Key insight: APIs are how different programs talk to each other. Your frontend talks to your backend via an API. Your backend might talk to Stripe's API for payments or Google's API for maps.

Request & Response Cycle

User clicks "Submit"
    ↓
Frontend sends HTTP request to backend
    ↓
Backend receives request, processes it
    ↓
Backend talks to database if needed
    ↓
Backend sends response back
    ↓
Frontend displays the result

Read the full file on GitHub · 55 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. 1mo ago First seen · 55 lines · 34 tokens per session scan A ff33cc8031a0

Subscribe to this mod's changes

backend is a skill published in the GitHub repository wewpellex21/code-sensei (3 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 673 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to backend, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

composio-community/awesome-claude-plugins · 61 tokens

aws-serverless-eda

AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions, EventBridge, SQS, SNS, and serverless…

zxkane/aws-skills · 112 tokens

java-clean-arch

Reviews or implements Clean Architecture / Hexagonal Architecture (Ports & Adapters) and DDD tactical patterns for Java projects. Use when user asks to "apply clean architecture", "implement hexagonal architecture", "add ports and adapters", "apply DDD", "refactor to clean arch", "review architecture", or "add value…

ducpm2303/claude-java-plugins · 68 tokens

java-cache

Use when the user asks to add caching, configure Redis or Caffeine cache, use @Cacheable/@CacheEvict/@CachePut, optimize repeated database or API calls, or review existing Spring Boot cache configuration.

ducpm2303/claude-java-plugins · 46 tokens

java-openapi

Generates or reviews OpenAPI / Swagger documentation for Spring Boot REST APIs — adds @Operation, @Schema, @ApiResponse annotations and configures Swagger UI. Use when user asks to "add Swagger", "document this API", "generate OpenAPI spec", "add @Operation annotations", "set up Swagger UI", or "document endpoints".

ducpm2303/claude-java-plugins · 69 tokens

java-api-review

Reviews Java REST API design including HTTP methods, status codes, naming, and versioning. Use when user asks to "review my API", "check REST design", "is this good REST", "review endpoints", "API design review", "check my controller", or "review HTTP API".

ducpm2303/claude-java-plugins · 59 tokens