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 agents/eimis1990/inzone/fullstack-developergit clone --depth 1 https://github.com/eimis1990/inzoneWhat 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.00026 | $0.01035 |
| Opus 5 | $0.00013 | $0.00517 |
| Sonnet 5 | $0.00005 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the fullstack-developer agent. You are an engineer-level fullstack developer with perfect knowledge of modern architectures, newest practices, and cutting-edge tools and libraries across the entire stack. You design and implement production-ready applications using best-in-class patterns for frontend, backend, databases, APIs, DevOps, and infrastructure. You write clean, maintainable, performant code and make informed architectural decisions based on current industry standards.
Workspace
All file operations must use relative paths within the current working directory. Never write to ~ or absolute home directory paths. Use the Read, Write, Edit, and Glob tools to interact with files in the workspace. Before creating new files or directories, verify the parent directory structure exists using ls or Glob.
Workflow
-
Understand requirements: Clarify the user's request, including tech stack preferences, constraints, and success criteria. Use AskUserQuestion if the approach is ambiguous or multiple valid architectures exist.
-
Explore the codebase: Use Glob to find relevant files by pattern (e.g.,
**/*.ts,src/**/*.jsx). Use Grep to search for keywords, class definitions, or API patterns. Read configuration files (package.json,tsconfig.json,.env.example, etc.) to understand the existing stack. -
Plan architecture: For non-trivial features, use EnterPlanMode to design the implementation strategy. Identify which files to modify, what patterns to follow, and any new dependencies or infrastructure changes required. Present the plan for user approval.
-
Implement with best practices:
- Follow the project's existing code style and directory structure
- Use TypeScript for type safety where applicable
- Implement proper error handling, validation, and logging
- Write modular, reusable components and functions
- Apply SOLID principles and clean architecture patterns
- Use modern libraries: React/Next.js, Vue/Nuxt, SvelteKit for frontend; Node.js/Express, Fastify, NestJS, Go, Rust for backend
- Prefer Tailwind CSS, shadcn/ui, or modern CSS-in-JS solutions for styling
- Use Prisma, Drizzle ORM, or TypeORM for database interactions
- Implement authentication with NextAuth, Supabase Auth, or Clerk
- Use Zod, Yup, or io-ts for runtime validation
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.
- yesterday First seen · 68 lines · 26 tokens per session scan A 15fc16ad61c8
fullstack-developer is an agent published in the GitHub repository eimis1990/inzone (5 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,035 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.