backend

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

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.

agentmods
npx agentmods add skills/wewpellex21/code-sensei/backend
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.

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. Scan, not verified.
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 $0.00034 $0.00673
Opus 5 $0.00017 $0.00336
Sonnet 5 $0.00007 $0.00135
Haiku 4.5 $0.00003 $0.00067

Measured 2d ago against content hash ff33cc8031a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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. 2d 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.0002 per session on Opus 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

agent-squad-python

Use when building or modifying a Python app that uses the agent-squad Python package — async multi-agent orchestration for Python 3.11+: orchestrator, agents (BedrockLLMAgent, AnthropicAgent, OpenAIAgent, SupervisorAgent, GroundedAgent, ChainAgent, and more), classifier routing (Bedrock, Anthropic, OpenAI), storage…

2FastLabs/agent-squad · 113 tokens

agent-squad-swift

Use when building or modifying a Swift app that uses the AgentSquad Swift framework — on-device multi-agent orchestration for iOS 16+ / macOS 14+: orchestrator, agents (Agent, GroundedAgent), classifier routing, LLM clients (OpenAI-compatible), tools (native + MCP), tool UIs/widgets, on-device storage, tracing, and…

2FastLabs/agent-squad · 91 tokens

agent-squad-typescript

Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…

2FastLabs/agent-squad · 87 tokens

run-integ

Run integration tests (deploy + destroy) against real AWS. Use when you need to verify cdkd works end-to-end with actual AWS resources.

go-to-k/cdkd · 34 tokens

verify-pr

Comprehensive PR readiness check before merge. Run quality checks, tests, CI, documentation, AWS resource cleanup, and code review.

go-to-k/cdkd · 29 tokens

review-pr

Recommend the right reviewer count for a PR based on size + bias factors. Outputs a concrete plan (inline spot-check / 1 reviewer / 3-axis parallel) plus ready-to-paste Agent dispatch prompts when reviewers are warranted.

go-to-k/cdkd · 49 tokens