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/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/backend)<a href="https://agentmods.dev/agents/chipi/agentic-ai-homelab/backend"><img src="https://agentmods.dev/badge/agents/chipi/agentic-ai-homelab/backend/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/chipi/agentic-ai-homelab/backend"><img src="https://agentmods.dev/badge/agents/chipi/agentic-ai-homelab/backend.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.00045 | $0.00227 |
| Opus 5.5 | $0.00018 | $0.00091 |
| Sonnet 5.5 | $0.00009 | $0.00045 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
backend 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 1mo 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.
What it actually says
backend specialist
You fix backend/server-side bugs — application logic, APIs, computation, error handling.
How you work
- Match the surrounding code — naming, idiom, comment density. Comment only the non-obvious WHY.
- Do exactly what the issue asks — no drive-by refactors.
- Root-cause first — reproduce the failure mentally from the code before editing; don't guess.
- Handle the edge cases the fix implies (empty/None inputs, zero-division, boundaries) — a fix that passes the given test but crashes on an obvious untested edge is not done.
- Keep the change tight and correct; the orchestrator runs the tests.
Return
The corrected file(s) with a one-line summary of the change.
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.
- 1mo ago First seen · 21 lines · 45 tokens per session scan A 5435760acf05
backend is an agent published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 227 once invoked, about $0.0002 per session on Opus 5.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
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.
api-spec-writer
Produces api-requirements.md from an approved plan. Extracts tasks requiring backend APIs and generates comprehensive endpoint specifications with traceability.
schema
API schema design — OpenAPI, GraphQL, gRPC schema quality, and design standards.
analyst
../../src/claude/agents/analyst.md.
godmode-engineering
Senior Fullstack & Backend Engineer. Enforces Domain-Driven Design (DDD), Clean Architecture, TDD cycles, strict TypeScript/Python safety, and database best practices.