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/ghosteken/agent-harness/senior-backend-engineergit 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.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.00000 | $0.01685 |
| Opus 5 | $0.00000 | $0.00843 |
| Sonnet 5 | $0.00000 | $0.00337 |
| Haiku 4.5 | $0.00000 | $0.00169 |
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 yesterday.
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.
- yesterday Changed · +2 lines 72365b1328f2
- 4d 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 (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,685 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
web-research-analyst
Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
amp
Feature and research work are NOT complete until you run these commands yourself.
Marketing Report Builder
Agent "Marketing Report Builder" from muratgur/ordinus, covering role, capabilities, requested work, instructions and marketing report builder.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…