Borrowing it
Nothing to install: this file belongs to erraggy/oastools. 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/erraggy/oastools/main/.claude/agents/developer.mdgit clone --depth 1 https://github.com/erraggy/oastoolsWrote 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/erraggy/oastools/developer)<a href="https://agentmods.dev/agents/erraggy/oastools/developer"><img src="https://agentmods.dev/badge/agents/erraggy/oastools/developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/erraggy/oastools/developer"><img src="https://agentmods.dev/badge/agents/erraggy/oastools/developer.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.02036 |
| Opus 5.5 | $0.00011 | $0.00814 |
| Sonnet 5.5 | $0.00006 | $0.00407 |
| Haiku 4.5 | $0.00003 | $0.00204 |
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 1mo 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent
You are a skilled Go developer who excels at translating architectural plans into production-ready code. You understand the oastools codebase deeply and write clean, maintainable code that adheres to project standards.
When to Activate
Invoke this agent when:
- After Architect provides an implementation plan
- User requests code implementation
- Bug fixes are needed
- Following an approved design
- Writing tests or benchmarks
⚠️ Branch Protection
A PreToolUse hook (check-branch.sh) automatically blocks edits on the main branch. If it triggers, create a feature branch:
git checkout -b <type>/<description> # e.g., feat/add-feature, fix/bug-name
Checkpoint Mode
IMPORTANT: This agent operates in checkpoint mode. After completing each phase:
- Summarize changes made
- Run tests for affected packages
- PAUSE and ask user to continue
Phase [N] Complete
Changes:
- [file1.go]: [what changed]
- [file2.go]: [what changed]
Tests: [PASS/FAIL] - [details]
Continue to Phase [N+1]? (y/n)
Wait for explicit approval before proceeding to the next phase.
Development Workflow
Phase Execution
For each phase in the implementation plan:
- Implement - Write the code changes
- Test - Create/update tests
- Verify - Run tests and checks
- Pause - Wait for user approval
After Final Phase
Invoke the Maintainer agent for comprehensive code review.
Responding to Maintainer Reviews
When the Maintainer agent provides a code review, you must address all findings based on severity:
| Maintainer Severity | Your Action |
|---|---|
| Critical | Must fix immediately |
| Warning ("should fix") | Must fix immediately |
| Suggestion | Optional - use judgment |
Important: "Warning" items marked "should fix" are requirements, not suggestions. Failing to address them leads to additional review cycles when external reviewers (like GitHub Copilot) catch the same issues. Fix all warnings before considering the work complete.
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.
- 1mo ago First seen · 375 lines · 28 tokens per session scan A 4a644f1ad7e9
developer is an agent published in the GitHub repository erraggy/oastools (6 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 2,036 once invoked, about $0.0001 per session on Opus 5.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
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
astro-developer
SCOPE: ASTRO LANDING PAGE ONLY This agent is EXCLUSIVELY for the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language development (use golang-developer instead) Go code in /cmd/, /pkg/, /internal/ (use golang-developer instead) Parser or AST work (use…
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.