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 skills/sandraschi/filesystem-mcp/full-stack-developernpx skills add sandraschi/filesystem-mcp --skill full-stack-developergit clone --depth 1 https://github.com/sandraschi/filesystem-mcpWhat 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.00025 | $0.03829 |
| Opus 5 | $0.00013 | $0.01914 |
| Sonnet 5 | $0.00005 | $0.00766 |
| Haiku 4.5 | $0.00003 | $0.00383 |
Grade A, and why
full-stack-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 2d 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.
This is a copy
100% identical to full-stack-developer — 0 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.
How it starts
The opening of the file, as written. The whole thing — 566 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Stack Developer
Overview
Master modern fullstack development with comprehensive guidance on building production-ready web applications. From concept to deployment, this skill covers everything from architecture design to DevOps, including the revolutionary SOTA Fullstack App Builder script that generates complete applications in minutes.
When to Use This Skill
Activate for:
- Building complete web applications (frontend + backend + infrastructure)
- Choosing technology stacks and architectural patterns
- Implementing modern development workflows and automation
- Setting up CI/CD pipelines and deployment strategies
- Integrating AI/ML capabilities into web applications
- Using the SOTA Fullstack App Builder for rapid prototyping
- Scaling applications from MVP to enterprise-grade systems
Core Capabilities
🏗️ Application Architecture
- Modern Web Stacks: React/Next.js + FastAPI/Node.js + databases
- Microservices vs Monoliths: When to choose each approach
- API Design: REST, GraphQL, and real-time communication
- State Management: Client-side, server-side, and distributed state
⚡ Rapid Development Tools
- SOTA Fullstack Builder: Generate production apps in minutes
- Code Generators: Scaffolding tools and boilerplates
- Low-Code Platforms: When and how to use them effectively
- AI-Assisted Development: GitHub Copilot, Cursor, and Claude integration
🤖 AI Integration
- AI ChatBots: Multi-provider support (OpenAI, Anthropic, Ollama)
- RAG Systems: Retrieval-augmented generation for applications
- Streaming Responses: Real-time AI interaction patterns
- Prompt Engineering: Effective AI integration techniques
🐳 Containerization & Orchestration
- Docker Best Practices: Multi-stage builds, security, optimization
- Kubernetes Patterns: Deployment, scaling, service meshes
- Cloud-Native: 12-factor apps, cloud platforms, serverless
📊 Monitoring & Analytics
- Application Monitoring: Health checks, error tracking, performance
- User Analytics: Usage patterns, conversion tracking, A/B testing
- Business Intelligence: Data visualization, reporting dashboards
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 566 lines · 25 tokens per session scan A 2c6139022428
full-stack-developer is a skill published in the GitHub repository sandraschi/filesystem-mcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 3,829 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to full-stack-developer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
freecad-expert
FreeCAD MCP is a FastMCP 3.4+ server providing 46+ CAD/CAM/CAE tools. It operates through a TCP bridge to FreeCAD GUI or via FreeCADCmd subprocess fallback.
session-context
FreeCAD MCP session context — CAD, BIM, CFD, FEM, 3D printing tool surface overview.
add-localization
Add or update a language translation in the privacy policy generator. Trigger when user says: "add {language} translation", "add locale", "translate to {language}", "add localization for {language}", or when a user wants to contribute a new language.
add-thirdparty-service
Add a new third-party service to the privacy policy generator. Trigger when user says: "add {name} service", "add third party service", "add 3rd party service", "add new service entry", or when a user wants to contribute a new service to the app.
dev-pipeline
Full feature-development pipeline for this repo — isolated worktree, spec, implementation plan, TDD build, quality gates, then a review→fix loop that only stops when review passes. Each stage delegates to a named project subagent (spec-researcher, pattern-scout, pipeline-implementer, pipeline-simplifier…
shrink-mcp-tool-docs
Shrink LLM-facing MCP tool descriptions — @mcp.tool docstrings and Field(description=...) — to eval-failure boundary via compress→eval→compress loop with snapshot+rollback, all gates green. Use when asked shrink/compress/optimize/token-diet tool descriptions, docstrings, or param descriptions. NOT for ordinary code…