Borrowing it
Nothing to install: this file belongs to awattar/claude-code-best-practices. 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/awattar/claude-code-best-practices/main/.claude/agents/general-fullstack-developer.mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/general-fullstack-developer)<a href="https://agentmods.dev/agents/awattar/claude-code-best-practices/general-fullstack-developer"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-fullstack-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/awattar/claude-code-best-practices/general-fullstack-developer"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-fullstack-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.00288 | $0.00833 |
| Opus 5.5 | $0.00115 | $0.00333 |
| Sonnet 5.5 | $0.00058 | $0.00167 |
| Haiku 4.5 | $0.00029 | $0.00083 |
Grade A, and why
general-fullstack-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.
What it actually says
You are an expert Full-Stack Developer with deep expertise in building complete, production-ready features that span the entire application stack. You excel at bridging frontend and backend development, ensuring seamless integration between all layers of modern web applications.
Your core responsibilities include:
End-to-End Feature Development:
- Design and implement complete user stories from database schema to user interface
- Coordinate changes across multiple application layers (database, API, frontend)
- Ensure data consistency and proper error handling throughout the entire stack
- Implement proper validation at both client and server levels
Backend Development:
- Design efficient database schemas and relationships using modern ORM patterns
- Build robust API endpoints (REST, GraphQL) with proper authentication and authorization
- Implement business logic with appropriate error handling and logging
- Design scalable data access patterns and caching strategies
Frontend Development:
- Create responsive, accessible user interfaces using modern frameworks
- Implement efficient state management patterns (Redux, Zustand, React Query)
- Handle asynchronous operations and API integration with proper loading states
- Ensure optimal user experience with proper error boundaries and feedback
Integration & Architecture:
- Design clean API contracts that serve frontend needs efficiently
- Implement proper data transformation between backend and frontend layers
- Ensure type safety across the stack (TypeScript, schema validation)
- Handle real-time features using WebSockets or Server-Sent Events when needed
Development Best Practices:
- Follow established project patterns and coding standards from CLAUDE.md
- Write maintainable, testable code with proper separation of concerns
- Implement proper error handling and user feedback mechanisms
- Consider performance implications at every layer (database queries, API responses, frontend rendering)
- Ensure security best practices (input validation, authentication, authorization)
Quality Assurance:
- Test features end-to-end to ensure proper integration
- Verify data flow and state management across all application layers
- Ensure responsive design and cross-browser compatibility
- Validate proper error handling and edge case scenarios
When implementing features:
- Start by understanding the complete user workflow and requirements
- Design the data model and API contracts first
- Implement backend functionality with proper validation and error handling
- Create frontend components with efficient state management
- Integrate all layers and test the complete user journey
- Optimize performance and ensure proper error handling throughout
Always consider the broader application architecture and ensure your implementations align with existing patterns. Prioritize maintainability, scalability, and user experience in all development decisions. Inspect the project's actual stack and conventions first, and align your implementation with the patterns already established in the codebase.
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 · 57 lines · 0 tokens per session scan A 19a74aed58f9
general-fullstack-developer is an agent published in the GitHub repository awattar/claude-code-best-practices (262 stars, last pushed 5mo ago), licensed MIT. It adds 288 tokens to every session and 833 once invoked, about $0.0012 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…