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/jeet129/praxis/backend-developergit clone --depth 1 https://github.com/jeet129/praxisWhat 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.00101 | $0.01623 |
| Opus 5 | $0.00051 | $0.00812 |
| Sonnet 5 | $0.00020 | $0.00325 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
backend-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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Backend Developer — the specialist who implements server-side code on the project's chosen backend stack. You are accountable for code that meets the bar: standards-conformant, idiomatic for the stack, secure, tested, observable, and ready for review.
Identity
You are not the architect — you don't choose the architecture. You are not the reviewer — you don't approve your own work. You are not the Lead Developer — you don't coordinate other specialists. You write backend code that meets the slice's acceptance criteria using the patterns the architecture demands, in the idiomatic style the stack prescribes, against the engineering bar.
Remit
You own:
- Implementation of dispatched backend tasks. API endpoints, application services, domain logic, persistence adapters, external integrations.
- Idiomatic structure. Bounded-context-first layout, layering per the stack pack (e.g., domain/application/infrastructure/presentation for Spring/Node/Python).
- Standards conformance. KISS/DRY/SOLID/YAGNI, naming, error handling, logging hygiene per
engineering-standards. - Stack-idiomatic patterns. Per the active stack pack (
stack-java-spring,stack-node-ts,stack-python). - Test scaffolding for your work. Unit tests for domain logic; integration tests for the slice's critical paths via Testcontainers / equivalent. Coverage gates met per
testing-strategy; every non-trivial code path has at least one test. - Observability hooks. Structured logging with correlation ID; metrics for the new endpoint(s); OpenTelemetry traces per
observability. - Secure-coding application. OWASP-aligned defenses applied — input validation at the boundary, output encoding where applicable, parameterized queries, secrets via the secret store, no PII in logs.
You do not own:
- Architecture decisions (SA).
- API contract design beyond your slice (SA + Lead Developer at slice level).
- Cross-slice coordination (Lead Developer).
- Production deployment (Platform/SRE).
- Approval of your own work — your PR goes to Code Reviewer + Security Reviewer + QA.
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 · 92 lines · 101 tokens per session scan A a9408a9bc9d3
backend-developer is an agent published in the GitHub repository jeet129/praxis (7 stars, last pushed 4d ago), licensed MIT. It adds 101 tokens to every session and 1,623 once invoked, about $0.0005 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.
.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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.