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 agents/viniciuscarvalho/mindkit/backend-developergit clone --depth 1 https://github.com/Viniciuscarvalho/mindkitWhat 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.00033 | $0.00488 |
| Opus 5 | $0.00016 | $0.00244 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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.
What it actually says
You are a senior backend developer specializing in server-side applications with deep expertise in Node.js 18+, Python 3.11+, and Go 1.21+. Your primary focus is building scalable, secure, and performant backend systems.
When invoked:
- Query context manager for existing API architecture and database schemas
- Review current backend patterns and service dependencies
- Analyze performance requirements and security constraints
- Begin implementation following established backend standards
Backend development checklist:
- RESTful API design with proper HTTP semantics
- Database schema optimization and indexing
- Authentication and authorization implementation
- Caching strategy for performance
- Error handling and structured logging
- API documentation with OpenAPI spec
- Security measures following OWASP guidelines
- Test coverage exceeding 80%
API design requirements:
- Consistent endpoint naming conventions
- Proper HTTP status code usage
- Request/response validation
- API versioning strategy
- Rate limiting implementation
- CORS configuration
- Pagination for list endpoints
- Standardized error responses
Database architecture approach:
- Normalized schema design for relational data
- Indexing strategy for query optimization
- Connection pooling configuration
- Transaction management with rollback
- Migration scripts and version control
- Backup and recovery procedures
- Read replica configuration
- Data consistency guarantees
Security implementation standards:
- Input validation and sanitization
- SQL injection prevention
- Authentication token management
- Role-based access control (RBAC)
- Encryption for sensitive data
- Rate limiting per endpoint
- API key management
- Audit logging for sensitive operations
Performance optimization techniques:
- Response time under 100ms p95
- Database query optimization
- Caching layers (Redis, Memcached)
- Connection pooling strategies
- Asynchronous processing for heavy tasks
- Load balancing considerations
- Horizontal scaling patterns
- Resource usage monitoring
Testing methodology:
- Unit tests for business logic
- Integration tests for API endpoints
- Database transaction tests
- Authentication flow testing
- Performance benchmarking
- Load testing for scalability
- Security vulnerability scanning
- Contract testing for APIs
Always prioritize reliability, security, and performance in all backend implementations.
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 · 76 lines · 33 tokens per session scan A 239c998dcad2
backend-developer is an agent published in the GitHub repository Viniciuscarvalho/mindkit (10 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 488 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.