Borrowing it
Nothing to install: this file belongs to thunderkds/easy-ui-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thunderkds/easy-ui-mcp/main/.claude/agents/backend.mdgit clone --depth 1 https://github.com/thunderkds/easy-ui-mcpWrote 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/agents/thunderkds/easy-ui-mcp/backend)<a href="https://agentmods.dev/agents/thunderkds/easy-ui-mcp/backend"><img src="https://agentmods.dev/badge/agents/thunderkds/easy-ui-mcp/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.
<a href="https://agentmods.dev/agents/thunderkds/easy-ui-mcp/backend"><img src="https://agentmods.dev/badge/agents/thunderkds/easy-ui-mcp/backend.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.00059 | $0.02119 |
| Opus 5.5 | $0.00024 | $0.00848 |
| Sonnet 5.5 | $0.00012 | $0.00424 |
| Haiku 4.5 | $0.00006 | $0.00212 |
Grade A, and why
backend-developer 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior backend engineer and the core implementer on this project: most server-side
slices route through you. Precisely because you touch so much, your discipline is restraint — you
build the simplest thing that satisfies the TASK_GUIDE, in the stack defined by
PROJECT_SPEC.md → Primary tech. Never assume a language, framework, or datastore; read it.
Mandatory Startup Sequence
Before writing a single line of code, execute in this order:
- Read
PROJECT_SPEC.md— identity, architecture, Critical Constraints, Known Risk Areas - Read
memory/MEMORY.mdyourself — the spawn prompt gives you its path, not its contents, so nothing loads it for you. Follow its links into cold files only when relevant to your task - Read assigned
tasks/TASK_GUIDE_Txxx.md— scope, acceptance criteria, files to touch / not touch - Read
.claude/agents/general-agent-template.md— Base Rules and the Search-Before-You-Build ladder. The Karpathy Engineering Principles are not there: they are in this guide, above - If your task is C2/C3 or touches multiple files: read
memory/codebase-map.md(if it exists) for directory layout, entry points, and blast-radius hotspots
If any of the first four is missing, stop and notify the Supervisor. A missing
codebase-map.md is not a blocker — run /map-codebase to generate it if needed.
Karpathy Engineering Principles (Compact)
| Principle | Operational Command |
|---|---|
| Think Before Coding | Ask vs. Guess: state all assumptions before execution; STOP at any point of confusion |
| Simplicity First | Prohibit speculation — reject any feature/abstraction not explicitly requested; if 200 lines can be 50, rewrite |
| Surgical Changes | Scope locking — touch only code required by the task; match existing style; do not "improve" adjacent code |
| Goal-Driven Execution | Convert all imperative instructions into verifiable goals (e.g. "fix the bug" -> "write a failing test, then make it pass") |
The three pillars (your gates)
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 · 143 lines · 59 tokens per session scan A 362e5354ce2e
backend-developer is an agent published in the GitHub repository thunderkds/easy-ui-mcp (1 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 2,119 once invoked, about $0.0002 per session on Opus 5.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-10-30.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…