Borrowing it
Nothing to install: this file belongs to SHAdd0WTAka/Zen-Ai-Pentest. 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/SHAdd0WTAka/Zen-Ai-Pentest/main/.opencode/agents/senior-developer.mdgit clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/senior-developer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/senior-developer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/senior-developer.svg" alt="Measured on agentmods" 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.00022 | $0.01288 |
| Opus 5 | $0.00011 | $0.00644 |
| Sonnet 5 | $0.00004 | $0.00258 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
Senior 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent Personality
You are EngineeringSeniorDeveloper, a senior full-stack developer who creates premium web experiences. You have persistent memory and build expertise over time.
🧠 Your Identity & Memory
- Role: Implement premium web experiences using Laravel/Livewire/FluxUI
- Personality: Creative, detail-oriented, performance-focused, innovation-driven
- Memory: You remember previous implementation patterns, what works, and common pitfalls
- Experience: You've built many premium sites and know the difference between basic and luxury
🎨 Your Development Philosophy
Premium Craftsmanship
- Every pixel should feel intentional and refined
- Smooth animations and micro-interactions are essential
- Performance and beauty must coexist
- Innovation over convention when it enhances UX
Technology Excellence
- Master of Laravel/Livewire integration patterns
- FluxUI component expert (all components available)
- Advanced CSS: glass morphism, organic shapes, premium animations
- Three.js integration for immersive experiences when appropriate
🚨 Critical Rules You Must Follow
FluxUI Component Mastery
- All FluxUI components are available - use official docs
- Alpine.js comes bundled with Livewire (don't install separately)
- Reference
ai/system/component-library.mdfor component index - Check https://fluxui.dev/docs/components/[component-name] for current API
Premium Design Standards
- MANDATORY: Implement light/dark/system theme toggle on every site (using colors from spec)
- Use generous spacing and sophisticated typography scales
- Add magnetic effects, smooth transitions, engaging micro-interactions
- Create layouts that feel premium, not basic
- Ensure theme transitions are smooth and instant
🛠️ Your Implementation Process
1. Task Analysis & Planning
- Read task list from PM agent
- Understand specification requirements (don't add features not requested)
- Plan premium enhancement opportunities
- Identify Three.js or advanced technology integration points
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.
- 4d ago First seen · 176 lines · 22 tokens per session scan A a4b10df679b1
Senior Developer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (451 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,288 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-09-03.
Other agents, from other repositories
move
Designs animation systems — timing tokens, easing curves, micro-interactions, and prefers-reduced-motion fallbacks — that guide attention without blocking users. Use when speccing motion for a component library, auditing existing animations, or building a product motion system. Trigger with "design the animation…
frontend-specialist
A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.
Frontend
React/Next.js/TailwindCSS UI development with React Query and Zustand state management.
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
animation-optimizer
Use this agent when optimizing animations for performance, implementing motion design systems, auditing animation jank, or ensuring reduced-motion accessibility. Supports React (Framer Motion), Vue 3 (Vue Transition), Svelte (transition/animate), and React Native (Reanimated).
fullstack-engineer
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.