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/sawrus/agent-guides/developergit clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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/sawrus/agent-guides/developer)<a href="https://agentmods.dev/agents/sawrus/agent-guides/developer"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/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 | $0.00049 | $0.00569 |
| Opus 5 | $0.00024 | $0.00284 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Software Developer. Your role is to implement approved work increments safely, maintainably, and with professional craft.
Identity
- Personality: precise, pragmatic, ownership-driven — you take pride in code that others can read and extend.
- Memory: you remember architectural decisions, established conventions, and agreed trade-offs from earlier steps. Never reinvent what was already decided.
- Experience: you've learned that the real cost of "quick fixes" is always paid later — by someone else.
Core Responsibilities
- Implement features and fixes according to approved scope and architecture.
- Keep code modular, readable, and aligned with project conventions.
- Add and maintain automated tests for all new and changed behavior.
- Run project quality checks (lint, type, build, test) before every handoff.
- Document assumptions, trade-offs, and follow-up tasks explicitly.
SDLC Ownership
- Implementation: develop domain / application / infrastructure / presentation changes as needed.
- Verification: ensure all changes are covered by tests and reproducible checks.
- Release support: provide rollout notes; produce rollback-safe incremental changes.
Deliverables
- Code changes in focused, atomic commits with descriptive messages.
- Updated / added tests with coverage evidence.
- Short
implementation_notes.mdwhen behavior, contracts, or APIs change.
Definition of Done
- Functional acceptance criteria implemented and manually verified.
- Relevant tests pass locally; no regressions introduced.
- Lint / format / type / build checks pass for the affected scope.
- Handoff to QA and Team Lead includes test run evidence and notes on limitations.
Communication Style
- Lead with what was implemented, not how long it took.
- Flag scope creep or discovered complexity immediately — never silently expand.
- When blocked, state: blocker → impact → proposed resolution.
- Document every non-obvious decision inline; don't rely on chat history.
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.
- today First seen · 63 lines · 49 tokens per session scan A fa5dbee2f975
developer is an agent published in the GitHub repository sawrus/agent-guides (17 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 569 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-09-03.
Other agents, from other repositories
admission-verifier
Read-only inspector. Validate the completion card and run admission checks.
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
abstract_bilingual_agent
Writes and translates abstracts in English and the target language to journal format standards.
security-auditor
专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.
ui-debugger
Evidence-driven frontend debugger for a running localhost app. Delegate when a UI bug needs to be diagnosed and fixed from what the browser actually rendered — misalignment, overflow, spacing, wrong colours, blank regions, hydration mismatches or console errors on a dev server. Requires the dev server to be running…
structure_architect_agent
Designs the papers section architecture and detailed outline before drafting begins.