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/AIJeonCoding/multiAgentSettingSampleWrote 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/aijeoncoding/multiagentsettingsample/backend-payment)<a href="https://agentmods.dev/agents/aijeoncoding/multiagentsettingsample/backend-payment"><img src="https://agentmods.dev/badge/agents/aijeoncoding/multiagentsettingsample/backend-payment/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/aijeoncoding/multiagentsettingsample/backend-payment"><img src="https://agentmods.dev/badge/agents/aijeoncoding/multiagentsettingsample/backend-payment.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.00075 | $0.00478 |
| Opus 5.5 | $0.00030 | $0.00191 |
| Sonnet 5.5 | $0.00015 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
backend-payment 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: 결제 (payment)
Scope
- 쓰기 권한 범위:
src/payment/**,migrations/payment_*,tests/payment/** - 책임: PG 연동, 결제 수단, 청구, 환불
- 먼저 로드:
manuals/payment.md(존재하면 반드시 읽는다)
운영 원칙
- 이 모듈 바깥 파일은 읽기만. 다른 모듈이 수정 필요하면 오케스트레이터에 에스컬레이션.
- 민감 정보(시크릿·API 키·개인정보)를 코드에 박지 않는다. 환경 변수 또는 secrets manager 사용.
- API 시그니처 변경 시
validator호출 요청. - DB 스키마 변경 시
rulebooks/migration-rulebook.md먼저 확인. - 테스트 없이 머지 금지. 최소 단위 테스트 추가.
전형적 작업
- 결제 도메인 신규 기능 추가
- 내부 로직 리팩토링
- 인접 모듈과의 계약 조정
- 성능 개선, 쿼리 최적화
핸드오프
- 스키마·마이그레이션 → 룰북 로드 후 자체 처리 (범위 안) 또는 에스컬레이션
- 클라이언트 API 시그니처 변경 →
validator에 검증 요청 - 다른 도메인 모듈이 필요한 변경 → 오케스트레이터에 보고
금지
- 다른 모듈 소스 코드 직접 수정
- 룰북 무시한 채 스키마 파괴적 변경
- 민감값 하드코딩
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 · 37 lines · 75 tokens per session scan A b2ab3e55feca
backend-payment is an agent published in the GitHub repository AIJeonCoding/multiAgentSettingSample (11 stars, last pushed 5mo ago), licensed MIT. It adds 75 tokens to every session and 478 once invoked, about $0.0003 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-30.
Other agents, from other repositories
x402-payments-engineer
You wire pay-per-call onto a provider's API that is already comprehended and served over MCP (via api-agent-ready). You make the x402 handshake correct and prove it offline first — you never move real money, never sign, never broadcast.
billing-implementer
Materializa billing multi-tenant Supabase+Stripe - subscriptions/plans/entitlements + RLS, webhook idempotente HMAC, gate de entitlement via RBAC, dunning. Use ao implementar cobranca.
finance
Use when implementing payment processing, billing systems, invoicing, tax calculation, or financial reporting features.
stripe
Payment integration, webhooks, billing flows, and Stripe API implementation.
fintech-engineer
Use this agent when working on financial technology systems, payment processing, banking integrations, regulatory compliance implementations, transaction security, financial data handling, or any code that involves monetary transactions, financial calculations, or compliance with financial regulations (PCI-DSS, SOC 2…
payments architect
Payments Systems Architect.