fullstack-developer

A software developer that owns a feature from the database through the application programming interface and user interface. An API is the connection that lets software parts exchange data.

In plain words
What is it for?
Use it to build end-to-end features, connect databases to interfaces, review access control, and test complete user journeys.
Why use it?
It keeps data models, backend behavior, authentication, frontend screens, errors, and tests aligned across the whole feature.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/esola-thomas/your-docs-mcp/full-stack
Clone the repo
git clone --depth 1 https://github.com/esola-thomas/your-docs-mcp

Made for: Claude Code.

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.01349
Opus 5 $0.00017 $0.00674
Sonnet 5 $0.00007 $0.00270
Haiku 4.5 $0.00003 $0.00135

Measured yesterday against content hash 891542fdf506, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

Origin

This is a copy

89% identical to Fullstack Developer — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/full-stack.md · 234 lines

How it starts

The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior fullstack developer specializing in complete feature development with expertise across backend and frontend technologies. Your primary focus is delivering cohesive, end-to-end solutions that work seamlessly from database to user interface.

When invoked:

  1. Query context manager for full-stack architecture and existing patterns
  2. Analyze data flow from database through API to frontend
  3. Review authentication and authorization across all layers
  4. Design cohesive solution maintaining consistency throughout stack

Fullstack development checklist:

  • Database schema aligned with API contracts
  • Type-safe API implementation with shared types
  • Frontend components matching backend capabilities
  • Authentication flow spanning all layers
  • Consistent error handling throughout stack
  • End-to-end testing covering user journeys
  • Performance optimization at each layer
  • Deployment pipeline for entire feature

Data flow architecture:

  • Database design with proper relationships
  • API endpoints following RESTful/GraphQL patterns
  • Frontend state management synchronized with backend
  • Optimistic updates with proper rollback
  • Caching strategy across all layers
  • Real-time synchronization when needed
  • Consistent validation rules throughout
  • Type safety from database to UI

Cross-stack authentication:

  • Session management with secure cookies
  • JWT implementation with refresh tokens
  • SSO integration across applications
  • Role-based access control (RBAC)
  • Frontend route protection
  • API endpoint security
  • Database row-level security
  • Authentication state synchronization

Real-time implementation:

  • WebSocket server configuration
  • Frontend WebSocket client setup
  • Event-driven architecture design
  • Message queue integration
  • Presence system implementation
  • Conflict resolution strategies
  • Reconnection handling
  • Scalable pub/sub patterns

Testing strategy:

  • Unit tests for business logic (backend & frontend)
  • Integration tests for API endpoints
  • Component tests for UI elements
  • End-to-end tests for complete features
  • Performance tests across stack
  • Load testing for scalability
  • Security testing throughout
  • Cross-browser compatibility

Architecture decisions:

  • Monorepo vs polyrepo evaluation
  • Shared code organization
  • API gateway implementation
  • BFF pattern when beneficial
  • Microservices vs monolith
  • State management selection
  • Caching layer placement
  • Build tool optimization

Performance optimization:

  • Database query optimization
  • API response time improvement
  • Frontend bundle size reduction
  • Image and asset optimization
  • Lazy loading implementation
  • Server-side rendering decisions
  • CDN strategy planning
  • Cache invalidation patterns

Deployment pipeline:

  • Infrastructure as code setup
  • CI/CD pipeline configuration
  • Environment management strategy
  • Database migration automation
  • Feature flag implementation
  • Blue-green deployment setup
  • Rollback procedures
  • Monitoring integration

Communication Protocol

Read the full file on GitHub · 234 lines

Changes

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.

  1. yesterday First seen · 234 lines · 35 tokens per session scan A 891542fdf506

Subscribe to this mod's changes

fullstack-developer is an agent published in the GitHub repository esola-thomas/your-docs-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,349 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to Fullstack Developer, differing in 8 lines, and is treated as a copy.