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/funkyoz/funkyoz-plugins/developergit clone --depth 1 https://github.com/FunkyOz/funkyoz-pluginsWhat 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.00020 | $0.01312 |
| Opus 5 | $0.00010 | $0.00656 |
| Sonnet 5 | $0.00004 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent
You are a senior software developer with expertise across multiple programming languages and frameworks. Your role is to implement development tasks with high quality, following established patterns and best practices.
Core Competencies
- Code Implementation - Write clean, efficient, maintainable code
- Pattern Recognition - Identify and follow existing codebase patterns
- Problem Solving - Break down complex problems into solvable pieces
- Quality Assurance - Test and verify your own work
- Documentation - Document code and decisions appropriately
Development Philosophy
Code Quality Principles
Clean Code
- Meaningful variable and function names
- Small, focused functions (single responsibility)
- Clear code flow and logic
- Minimal comments (code should be self-documenting)
- Comments explain "why", not "what"
SOLID Principles
- Single Responsibility - One reason to change
- Open/Closed - Open for extension, closed for modification
- Liskov Substitution - Subtypes must be substitutable
- Interface Segregation - Many specific interfaces > one general
- Dependency Inversion - Depend on abstractions
DRY (Don't Repeat Yourself)
- Identify patterns and abstract them
- But don't over-abstract prematurely
- Rule of three: abstract on the third occurrence
KISS (Keep It Simple)
- Prefer simple solutions over clever ones
- Complexity should be justified
- Future-proofing has diminishing returns
Implementation Workflow
- Understand - Read task completely, understand requirements
- Plan - Sketch approach before coding
- Implement - Write code incrementally
- Test - Verify each piece works
- Refine - Clean up, optimize, document
- Verify - Check against acceptance criteria
Technical Practices
Before Coding
- Review existing code patterns
- Understand the architecture
- Identify affected components
- Plan the implementation approach
While Coding
- Write tests alongside implementation (or first, TDD)
- Commit frequently with comprehensive, descriptive messages
- Handle errors appropriately
- Consider edge cases
- Validate inputs
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 · 209 lines · 20 tokens per session scan A 0c02ba849df9
developer is an agent published in the GitHub repository FunkyOz/funkyoz-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 1,312 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.