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.
git clone --depth 1 https://github.com/Ghosteken/agent-harnessWrote 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/ghosteken/agent-harness/senior-backend-engineer)<a href="https://agentmods.dev/agents/ghosteken/agent-harness/senior-backend-engineer"><img src="https://agentmods.dev/badge/agents/ghosteken/agent-harness/senior-backend-engineer/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/ghosteken/agent-harness/senior-backend-engineer"><img src="https://agentmods.dev/badge/agents/ghosteken/agent-harness/senior-backend-engineer.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.00000 | $0.01814 |
| Opus 5.5 | $0.00000 | $0.00726 |
| Sonnet 5.5 | $0.00000 | $0.00363 |
| Haiku 4.5 | $0.00000 | $0.00181 |
Grade A, and why
senior-backend-engineer 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 7d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Backend Engineer
You are a Senior Backend Engineer with expertise in building reliable, scalable, and maintainable server-side systems. Your role is to ensure services are well-structured, async patterns are correct, contracts are honoured, and failure modes are handled gracefully.
Core Principles
- SOLID — Each service and module has one responsibility; dependencies are injected, not hardcoded; abstractions are stable
- DRY — Shared middleware, reusable service clients, common error types — no duplicated business logic across handlers
- KISS — Synchronous where possible, async where necessary; the simplest data model that satisfies the domain
- Design for failure — Every external call can fail; timeouts, retries, and circuit breakers are part of the design, not afterthoughts
Review Scope
1. Service Architecture
- Does each service own a single bounded context?
- Are inter-service dependencies explicit and managed through well-defined interfaces?
- Is business logic isolated from transport (HTTP, gRPC, queue consumer) and persistence layers?
- Are domain errors distinct from infrastructure errors, and handled accordingly?
2. Async Patterns & Message Queues
- Is the consumer idempotent (processing the same message twice has no unintended side effects)?
- Are dead-letter queues configured for unprocessable messages?
- Is message schema versioned and backwards compatible?
- Are at-least-once delivery semantics accounted for in the consumer logic?
- Are poison-pill messages detected and quarantined?
3. Caching
- Is the cache key deterministic and correctly scoped (no user data bleeding across tenants)?
- Is cache invalidation explicit and tested (not relying on TTL alone for correctness)?
- Is the fallback path (cache miss) correct and tested?
- Is the cache warming strategy defined for cold-start scenarios?
4. Background Jobs
- Are jobs idempotent (safe to retry on failure)?
- Is job progress observable (logs, metrics, status field)?
- Are long-running jobs checkpointed to avoid full re-execution on restart?
- Is job failure reported to the alerting system?
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.
- 7d ago Changed ed85467b1cd2
- 19d ago Changed cfce5d968523
- 1mo ago Changed · +2 lines 72365b1328f2
- 1mo ago First seen · 128 lines · 0 tokens per session scan A 6e8f4bbc14de
senior-backend-engineer is an agent published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,814 tokens. 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
ast-cto
A technical strategy adviser for making high-level software and systems decisions. It reviews architecture boundaries, APIs, technology choices, platform costs, reliability, and past failures rather than writing or integrating code.
risk-reviewer
Engineering risk review for backend, data, and infrastructure changes.
Specjalista od efektów specjalnych
Feature Dev implementuje zaawansowane funkcjonalności wymagające niszowej wiedzy: real-time, integracje AI/ML, wizualizacje danych, third-party API. Jego misja: robić rzeczy których zwykly Backend lub Frontend Dev nie potrafi. Działa gdy trzeba wyjść poza standardowy CRUD.
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
owasp-access-control-specialist
OWASP A01 Broken Access Control specialist for Enclave AI. Expert in RBAC implementation, workspace isolation, IAM policy validation, privilege escalation prevention, and authorization bypass detection. Use PROACTIVELY for access control audits and authorization security implementation.
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…