Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. 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/Vinix24/vnx-orchestration/main/.claude/skills/backend-developer/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/backend-developer)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/backend-developer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/backend-developer/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/skills/vinix24/vnx-orchestration/backend-developer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/backend-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 95 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00016 | $0.01428 |
| Opus 5.5 | $0.00006 | $0.00571 |
| Sonnet 5.5 | $0.00003 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade B, and why
backend-developer scanned grade B with 1 finding 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 25d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer
Create fault-tolerant, scalable server-side solutions with focus on reliability and security.
Core Responsibilities
- Design data models and schemas
- Implement business logic with tests
- Create API endpoints with validation
- Add error handling and logging
- Optimize database queries
- Document API contracts
Core Principles
- Reliability First: Build fault-tolerant systems
- Security by Default: Validate inputs, sanitize outputs
- Performance Aware: Optimize queries, cache strategically
- API Design: RESTful conventions, clear contracts
Examples
- "Implement user authentication service"
- "Create data processing pipeline"
- "Build real-time event handler"
Guidelines
- Error Handling: Graceful degradation, meaningful messages
- Logging: Structured logs with correlation IDs
- Security: Input validation, SQL injection prevention
- Testing: Unit tests >80%, integration tests
- Database: Normalized design, indexed queries
API Development Standards
- Clear resource naming (/users, /products)
- HTTP status codes correctly used
- Request/response validation
- Rate limiting implemented
- Authentication/authorization checks
Performance Targets
- Response time <200ms p95
- Database queries <50ms
- Connection pooling configured
- Caching strategy defined
- Background jobs for heavy tasks
Quality Requirements
- PR under 300 lines
- Include unit and integration tests
- Update API documentation
- No breaking changes without versioning
- Follow existing patterns
Codex Defense Checklist (mandatory before commit)
These patterns recur in codex_gate findings. Apply preemptively.
File I/O
- Atomic writes: any rewrite of a persistent file (YAML, NDJSON, JSON config, schema files) MUST write to
<path>.tmpthenos.replace(tmp, path). Neveropen(path, 'w')directly on canonical state. - fcntl.flock for shared NDJSON: any read-then-rewrite of an NDJSON file consumed by live appenders MUST acquire
fcntl.flock(fd, fcntl.LOCK_EX)on the same lock the appenders use. Hold through atomic rename. - Subprocess stdin writes: wrap
proc.stdin.write()intry: ... except BrokenPipeError: return AdapterResult(status='failed', ...). Provider startup-failures must surface as structured failures, not raised exceptions.
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.
- 25d ago Changed b92a62cf83cc
- 1mo ago First seen · 112 lines · 16 tokens per session scan B 3013c7494c4b
backend-developer is a skill published in the GitHub repository Vinix24/vnx-orchestration (62 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,428 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-design-reviewer
Expert API design reviewer for REST, GraphQL, and gRPC APIs. Analyzes API designs for security, performance, consistency, scalability, and maintainability. Use when designing new APIs, reviewing API proposals, auditing existing endpoints, or before major API releases. Covers authentication, error handling, pagination…
node-backend
Node.js backend development patterns for Express, NestJS, Fastify, and Hono. Use when implementing APIs, authentication, middleware, services, and server-side logic with Node.js and TypeScript. Provides project structure, code patterns, and best practices.
system-design
System design patterns and architectural decision frameworks for web applications and iOS native apps. Use when making technology choices, selecting architecture patterns, designing APIs, choosing databases, planning authentication, or architecting mobile app backends. Provides comparison matrices for informed…
tushare
A Python interface for Tushare, a financial data service that provides market and company information for stocks, funds, futures, and digital assets. It returns queried data as pandas tables.
octopus-architecture
Review system architecture, simplify boundaries, or compare interface designs from repository evidence.
agenticx-tool-creator
Guide for creating custom tools in AgenticX including function decorator tools, MCP tool integration, tool registries, and remote tool access. Use when the user wants to create tools for agents, integrate external APIs as tools, build MCP servers, or extend agent capabilities with custom functions.