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 agentmods add skills/mdgrey33/claude_mind/backendnpx skills add MDGrey33/claude_mind --skill backendgit clone --depth 1 https://github.com/MDGrey33/claude_mindWrote 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/mdgrey33/claude_mind/backend)<a href="https://agentmods.dev/skills/mdgrey33/claude_mind/backend"><img src="https://agentmods.dev/badge/skills/mdgrey33/claude_mind/backend.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00668 |
| Opus 5 | $0.00008 | $0.00334 |
| Sonnet 5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
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 4d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Development Skill
Implement robust, secure, and performant backend systems.
When to Use
- Implementing API endpoints
- Writing business logic
- Database operations
- External integrations
- Background job processing
Code Quality Standards
Structure
- One responsibility per function
- Files < 500 lines
- Clear module boundaries
- Consistent naming conventions
Error Handling
// Good - Explicit error handling
try {
const result = await riskyOperation();
return { success: true, data: result };
} catch (error) {
logger.error('Operation failed', { error, context });
throw new AppError('OPERATION_FAILED', error.message);
}
Validation
// Validate at boundaries
function createUser(input) {
const validated = validateUserInput(input);
if (!validated.success) {
throw new ValidationError(validated.errors);
}
return userRepository.create(validated.data);
}
Database Operations
// Use transactions for multiple operations
await db.transaction(async (tx) => {
await tx.users.create(userData);
await tx.accounts.create(accountData);
await tx.notifications.create(welcomeNotification);
});
Common Patterns
Repository Pattern
class UserRepository {
async findById(id) { ... }
async findByEmail(email) { ... }
async create(data) { ... }
async update(id, data) { ... }
async delete(id) { ... }
}
Service Layer
class UserService {
constructor(userRepo, emailService) {
this.userRepo = userRepo;
this.emailService = emailService;
}
async registerUser(data) {
const user = await this.userRepo.create(data);
await this.emailService.sendWelcome(user);
return user;
}
}
Controller/Handler
async function createUserHandler(req, res) {
try {
const user = await userService.registerUser(req.body);
res.status(201).json({ data: user });
} catch (error) {
handleError(error, res);
}
}
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.
- 4d ago First seen · 138 lines · 16 tokens per session scan A 363129cb361e
backend is a skill published in the GitHub repository MDGrey33/claude_mind (2 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 668 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…