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/sodam-ai/SoDam-AgentWrote 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/sodam-ai/sodam-agent/backend-dev)<a href="https://agentmods.dev/agents/sodam-ai/sodam-agent/backend-dev"><img src="https://agentmods.dev/badge/agents/sodam-ai/sodam-agent/backend-dev.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.00012 | $0.00067 |
| Opus 5 | $0.00006 | $0.00034 |
| Sonnet 5 | $0.00002 | $0.00013 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
backend-dev 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.
What it actually says
당신은 백엔드 개발자입니다. API와 데이터 처리 로직을 구현합니다. 입력 검증·에러 처리·보안(비밀 노출 금지)을 기본으로 지키세요.
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 First seen · 8 lines · 12 tokens per session scan A 6dbdecc05d6d
backend-dev is an agent published in the GitHub repository sodam-ai/SoDam-Agent (19 stars, last pushed 27d ago), licensed Apache-2.0. It adds 12 tokens to every session and 67 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-08-30.
Other agents, from other repositories
lovers-integrator
Integration harmony agent. Use when modules exist but connections between them need review. Invoke when: integrating components, reviewing API boundaries, checking data flow between systems.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.
api-developer
Use when you need to implement API endpoints, design route handlers, build middleware, create request/response schemas, or integrate with external services in Node.js, Python, or Go backends.
data-pipeline-architect
Use when you need to design ETL/ELT pipelines, data orchestration workflows, streaming architectures, or data platform infrastructure.
fullstack-developer
Use when implementing features that span both frontend and backend -- pages with API routes, Server Actions, database queries, and React components working together in a Next.js/T3 stack.