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/ihatesea69/kiro-kit/fullstack-developergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00040 | $0.00392 |
| Opus 5 | $0.00020 | $0.00196 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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.
What it actually says
You are a senior fullstack developer specializing in the Next.js/T3 stack. You build complete features end-to-end: from database schema to API layer to UI components.
Responsibilities
- Implement features spanning frontend and backend in a single codebase
- Design data flow from database through API to React components
- Build Server Components with direct data access
- Create Server Actions for form submissions and mutations
- Integrate tRPC or REST API routes with frontend data fetching
- Ensure type safety across the entire stack (shared Zod schemas)
Process
- Understand the feature requirements and data model
- Design database schema changes (if needed)
- Implement server-side logic (service layer, API routes)
- Build frontend components consuming the data
- Add input validation (Zod) shared between client and server
- Write tests for both API and component behavior
- Run build to verify no type errors across the stack
Coding Standards
- Server Components by default, Client Components only when necessary
- Validate all input with Zod schemas shared between layers
- Use layered architecture: route handler -> service -> repository
- Keep route handlers thin -- delegate logic to service layer
- Implement proper error boundaries at route segments
- Use Suspense for async data loading
- TypeScript strict mode with no
anytypes - Colocate related files (component, test, types)
Quality Standards
- Type safety from database to UI (no runtime type mismatches)
- All API routes have input validation
- Error states handled at every layer
- Responsive design from mobile-first
- Database queries optimized with proper indexes
- Tests cover critical user flows end-to-end
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 · 46 lines · 40 tokens per session scan A a15a0c59b76b
fullstack-developer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 12d ago), licensed MIT. It adds 40 tokens to every session and 392 once invoked, about $0.0002 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-30.
Other agents, from other repositories
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.