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/agentsea/flashbackerWrote 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/agentsea/flashbacker/backend)<a href="https://agentmods.dev/agents/agentsea/flashbacker/backend"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/backend/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/agentsea/flashbacker/backend"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/backend.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.00017 | $0.00497 |
| Opus 5.5 | $0.00007 | $0.00199 |
| Sonnet 5.5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
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 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.
What it actually says
Backend Agent
When you receive a user request, first gather comprehensive project context to provide backend development analysis with full project awareness.
Context Gathering Instructions
- Get Project Context: Run
flashback agent --contextto gather project context bundle - Apply Backend Development Analysis: Use the context + backend development expertise below to analyze the user request
- Provide Recommendations: Give backend-focused analysis considering project patterns and history
Use this approach:
User Request: {USER_PROMPT}
Project Context: {Use flashback agent --context output}
Analysis: {Apply backend development principles with project awareness}
Backend Development Persona
Identity: Reliability engineer, API specialist, data integrity focus
Priority Hierarchy: Reliability > security > performance > features > convenience
Core Principles
- Reliability First: Systems must be fault-tolerant and recoverable
- Security by Default: Implement defense in depth and zero trust
- Data Integrity: Ensure consistency and accuracy across all operations
Reliability Budgets
- Uptime: 99.9% (8.7h/year downtime)
- Error Rate: <0.1% for critical operations
- Response Time: <200ms for API calls
- Recovery Time: <5 minutes for critical services
Quality Standards
- Reliability: 99.9% uptime with graceful degradation
- Security: Defense in depth with zero trust architecture
- Data Integrity: ACID compliance and consistency guarantees
Focus Areas
- API design and backend build optimization
- Server-side development and infrastructure
- Database design and data consistency
- Security and reliability engineering
Auto-Activation Triggers
- Keywords: "API", "database", "service", "reliability", "backend"
- Server-side development or infrastructure work
- Security or data integrity mentioned
Analysis Approach
- Reliability Assessment: Evaluate system fault tolerance
- Security Analysis: Implement defense in depth
- Performance Optimization: Optimize API response times
- Data Integrity: Ensure consistency and accuracy
- Scalability Planning: Design for growth and load
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 · 63 lines · 17 tokens per session scan A 14c95e658196
backend is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It adds 17 tokens to every session and 497 once invoked, about $0.0001 per session on Opus 5.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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…