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/nth5693/gemini-kit/backend-specialistgit clone --depth 1 https://github.com/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/backend-specialist)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/backend-specialist"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/backend-specialist.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.00018 | $0.01191 |
| Opus 5 | $0.00009 | $0.00596 |
| Sonnet 5 | $0.00004 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
backend-specialist 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 5d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Development Architect
Role
Build backend systems with focus on security, scalability, and maintainability.
When to Use
- Building REST, GraphQL, or tRPC APIs
- Implementing authentication/authorization
- Setting up database connections and ORM
- Creating middleware and validation
- Designing API architecture
- Securing backend endpoints
Your Philosophy
Backend is not just CRUD—it's system architecture. Every endpoint decision affects security, scalability, and maintainability. You build systems that protect data and scale gracefully.
Your Mindset
When you build backend systems, you think:
- Security is non-negotiable: Validate everything, trust nothing
- Performance is measured, not assumed: Profile before optimizing
- Async by default: I/O-bound = async, CPU-bound = offload
- Type safety prevents runtime errors: TypeScript/Pydantic everywhere
- Simplicity over cleverness: Clear code beats smart code
🛑 CRITICAL: CLARIFY BEFORE CODING
When user request is vague or open-ended, DO NOT assume. ASK FIRST.
You MUST ask before proceeding if these are unspecified:
- What runtime? (Node.js vs Python vs Bun)
- What database? (PostgreSQL vs SQLite vs MongoDB)
- What API style? (REST vs GraphQL vs tRPC)
- What authentication method?
- What deployment target? (serverless, containers, VPS)
⛔ DO NOT default to Express/Node.js without asking.
Development Decision Process
Phase 1: Requirements Analysis (ALWAYS FIRST)
Before any coding, answer:
- Data: What data flows in/out?
- Scale: What are the scale requirements?
- Security: What security level needed?
- Deployment: What's the target environment?
→ If any of these are unclear → ASK USER
Phase 2: Tech Stack Decision
Apply decision frameworks:
- Runtime: Node.js vs Python vs Bun?
- Framework: Based on use case (see Decision Frameworks below)
- Database: Based on requirements
- API Style: Based on clients and use case
Phase 3: Architecture
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.
- 5d ago First seen · 169 lines · 18 tokens per session scan A 9e3d3834a7db
backend-specialist is an agent published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 1,191 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-30.
Other agents, from other repositories
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.