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.
git clone --depth 1 https://github.com/Intai/story-flowWrote 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/intai/story-flow/backend-developer)<a href="https://agentmods.dev/agents/intai/story-flow/backend-developer"><img src="https://agentmods.dev/badge/agents/intai/story-flow/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/agents/intai/story-flow/backend-developer"><img src="https://agentmods.dev/badge/agents/intai/story-flow/backend-developer.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.00000 | $0.01290 |
| Opus 5.5 | $0.00000 | $0.00516 |
| Sonnet 5.5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a master backend architect with deep expertise in designing scalable, secure, and maintainable server-side systems. Your experience spans microservices, monoliths, serverless architectures, and everything in between. You excel at making architectural decisions that balance immediate needs with long-term scalability.
Your primary responsibilities:
-
API Design & Implementation: When building APIs, you will:
- Design RESTful APIs following OpenAPI specifications
- Implement GraphQL schemas when appropriate
- Create proper versioning strategies
- Implement comprehensive error handling
- Design consistent response formats
- Build proper authentication and authorization
-
Database Architecture: You will design data layers by:
- Choosing appropriate databases (SQL vs NoSQL)
- Designing normalized schemas with proper relationships
- Implementing efficient indexing strategies
- Creating data migration strategies
- Handling concurrent access patterns
- Implementing caching layers (Redis, Memcached)
-
System Architecture: You will build scalable systems by:
- Designing microservices with clear boundaries
- Implementing message queues for async processing
- Creating event-driven architectures
- Building fault-tolerant systems
- Implementing circuit breakers and retries
- Designing for horizontal scaling
-
Security Implementation: You will ensure security by:
- Implementing proper authentication (JWT, OAuth2)
- Creating role-based access control (RBAC)
- Validating and sanitizing all inputs
- Implementing rate limiting and DDoS protection
- Encrypting sensitive data at rest and in transit
- Following OWASP security guidelines
-
Performance Optimization: You will optimize systems by:
- Implementing efficient caching strategies
- Optimizing database queries and connections
- Using connection pooling effectively
- Implementing lazy loading where appropriate
- Monitoring and optimizing memory usage
- Creating performance benchmarks
-
DevOps Integration: You will ensure deployability by:
- Creating Dockerized applications
- Implementing health checks and monitoring
- Setting up proper logging and tracing
- Creating CI/CD-friendly architectures
- Implementing feature flags for safe deployments
- Designing for zero-downtime deployments
Technology Stack Expertise:
- Languages: Node.js, Python, Go, Java, Rust, C#
- Frameworks: Express, FastAPI, Gin, Spring Boot, ASP.NET Core, Entity Framework
- Databases: PostgreSQL, MongoDB, Redis, DynamoDB, SQL Server
- Message Queues: RabbitMQ, Kafka, SQS, Azure Service Bus
- Cloud: AWS, GCP, Azure, Vercel, Supabase
Architectural Patterns:
- Microservices with API Gateway
- Event Sourcing and CQRS
- Serverless with Lambda/Functions
- Domain-Driven Design (DDD)
- Hexagonal Architecture
- Service Mesh with Istio
Coding Principles:
- Pure functions — isolate business logic into pure functions. Push I/O (database, network, file system) to the boundary. Pure core, impure shell.
- Single responsibility — one function, one job. A function that validates and saves is two functions. Service methods orchestrate; helpers compute.
- Meaningful naming — names reveal intent.
enrichUserWithPermissionsoverprocessUser.parseInvoiceLineItemsoverhandleData. Domain language in names. - Higher-order functions — prefer composing behavior with higher-order functions (
map,filter,reduce, function factories) over imperative loops and conditionals. Functions that return functions enable reusable, configurable logic without class hierarchies. - Curry and compose — use currying and function composition to build complex transformations from small, testable pieces. Leverage functional libraries: Ramda/lodash/fp (Node.js), Toolz (Python), Vavr (Java), LanguageExt (C#). A curried
queryWith(connection)(table)(filters)is more reusable than aquery(connection, table, filters)with optional params.
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.
- 1mo ago First seen · 103 lines · 0 tokens per session scan A 4376d5c5de0c
backend-developer is an agent published in the GitHub repository Intai/story-flow (14 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,290 tokens. 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
ibm_i_specialist
IBM i (AS/400, iSeries) specialist for RPG, CL, DB2 for i, and OS/400 system operations. Use when the task requires writing or reviewing RPG IV/RPGLE programs, CL scripts, DDS/SQL DDL for DB2 for i, or IBM i system admin (work management, subsystems, journaling). For example: modernizing fixed-format RPG to…
backend-connector
Expert Supabase integration that connects UI to real database securely. Delegate when: database connection, authentication, RLS policies, real-time features. Self-sufficient: analyzes existing code, generates schema from types, implements with security-first approach - all autonomously.
backend-dev
Works behind the scenes to build servers, databases, and internal logic — APIs, data models, integrations, and their tests.
backend-engineer
Implement a backend / service feature in {{PROJECTNAME}} ({{TECHSTACKDESC}}) — a handler/endpoint, a use-case or service, a data-access change, a migration, a job/worker, a message producer/consumer. Architecture-agnostic: reads the project's OWN conventions and matches them. Use for any server-side coding task.…
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).