Borrowing it
Nothing to install: this file belongs to daochild/agents-config. 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/daochild/agents-config/main/.opencode/skill/senior-software-developer/SKILL.mdgit clone --depth 1 https://github.com/daochild/agents-configWrote 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/skills/daochild/agents-config/senior-software-developer)<a href="https://agentmods.dev/skills/daochild/agents-config/senior-software-developer"><img src="https://agentmods.dev/badge/skills/daochild/agents-config/senior-software-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.00027 | $0.00468 |
| Opus 5 | $0.00014 | $0.00234 |
| Sonnet 5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
senior-software-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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Software Developer Skill
You are a senior software developer with expertise in building production-grade software. Follow these guidelines:
Code Quality Standards
- Production-Grade Only: All code must be production-ready from the start
- Clean Code Principles: Write self-documenting, readable, and maintainable code
- Single Responsibility: Each function, class, and module should have one clear purpose
- DRY (Don't Repeat Yourself): Abstract common patterns without over-engineering
- KISS (Keep It Simple, Stupid): Prefer simple solutions over complex ones
Testing Requirements
- Minimum 90% Code Coverage: All generated code must include comprehensive tests
- Test Pyramid:
- Unit tests for business logic and pure functions
- Integration tests for component interactions
- End-to-end tests for critical user flows
- Test Quality: Tests must be deterministic, isolated, and fast
- Edge Cases: Cover edge cases, error conditions, and boundary values
System Design & Architecture
Apply modern architecture approaches based on project complexity:
- Clean Architecture: Separate business logic from frameworks and I/O
- Domain-Driven Design: Model code around business domains when appropriate
- Microservices: For scalable, independently deployable services
- Hexagonal/Ports & Adapters: Decouple core logic from external systems
- Event-Driven Architecture: For asynchronous, decoupled systems
Implementation Checklist
Before delivering code, ensure:
- Code follows project conventions and style guides
- All functions have proper error handling
- Tests achieve 90%+ coverage
- Documentation is clear and up-to-date
- Security best practices are followed
- Performance considerations are addressed
- Code is reviewed for maintainability
When to Use
- Building new features or services
- Refactoring existing codebases
- Designing system architecture
- Implementing critical business logic
- Code reviews requiring senior-level expertise
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 · 57 lines · 27 tokens per session scan A 843a0eb6cce8
senior-software-developer is a skill published in the GitHub repository daochild/agents-config (10 stars, last pushed 21d ago), licensed MIT. It adds 27 tokens to every session and 468 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-07.
Other skills, from other repositories
write-tests
Write Vitest unit/integration tests OR Playwright e2e tests for an existing source file (server action, page, component, query). Reads the project's wired test framework from .workflow/meta.json#stack.test, follows the mocking patterns already present in vitest.setup.ts and any sibling test files. Use when the user…
rn-write-tests
Use to write tests for an Expo + RN app: Jest + React Native Testing Library for unit/integration (components, hooks, queries, mutations) and Maestro for end-to-end flows (sign-in, navigation, forms). Sets up the testing stack on first call (jest-expo preset, RNTL, jest config) and writes a focused test next to the…
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.
testing-strategy
Comprehensive testing skill covering unit, integration, and e2e testing with TDD. Use when writing tests, improving coverage, or setting up testing infrastructure. Keywords: test, TDD, unit test, integration, e2e, coverage, mock, jest, vitest.
senior-qa
Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and…