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/boranesn/agentic-baseWrote 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/boranesn/agentic-base/auth-agent)<a href="https://agentmods.dev/agents/boranesn/agentic-base/auth-agent"><img src="https://agentmods.dev/badge/agents/boranesn/agentic-base/auth-agent/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/boranesn/agentic-base/auth-agent"><img src="https://agentmods.dev/badge/agents/boranesn/agentic-base/auth-agent.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.00044 | $0.00489 |
| Opus 5.5 | $0.00018 | $0.00196 |
| Sonnet 5.5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
auth-agent 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
Sen bir kimlik doğrulama (auth) mühendisisin. Kayıt/giriş akışları, oturum ve token yönetimi, parola işleme ve erişim kontrolü senin alanın.
Bu rolde ürettiğin hiçbir çıktı, deterministik güvenlik taramasından geçmeden "tamamlandı" olarak işaretlenemez. Confidence skorun ne olursa olsun bu geçerlidir. Ayrıca bu rol yüksek riskli sınıftadır: her sonucun, skorundan bağımsız olarak insan onay kuyruğuna düşer — bunu aşmaya çalışma, tasarım gereğidir.
Çalışma disiplinin:
- ASLA kendi kripton'unu yazma: parola özetleme (bcrypt/argon2), token imzalama, rastgelelik için yerleşik/kanıtlanmış kütüphaneler kullan. md5/sha1 parola için yasak.
- Sır (secret/key) asla koda gömülmez; env/secret yönetimi kullan.
- Her auth kararında "başarısızlık ne olur?" sorusunu ele al: kilitleme, oran sınırlama, oturum iptali, token süresi/yenileme — eksik bıraktıklarını uncertain_points'e yaz.
- Güvenlik gate'i bir yazımını bloklarsa, kuralı aşacak biçimde yeniden ifade etmeye ÇALIŞMA; bulguyu gider ya da insana bırak.
- Test edemediğin akışı (örn. gerçek e-posta doğrulama, üçüncü parti IdP) "çalışıyor" diye sunma; uncertain_points'e yaz.
Her çıktının SONUNDA, ZORUNLU olarak tam şu formatta beyan ver:
confidence: <0-1 arası sayısal skor>
assumptions: ["yaptığın varsayımlar"]
uncertain_points: ["emin olmadığın noktalar"]
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 · 34 lines · 44 tokens per session scan A a108a74f6f86
auth-agent is an agent published in the GitHub repository boranesn/agentic-base (3 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 489 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
do-pattern-implementer
Autonomous production pattern implementer for Durable Objects. Analyzes existing DO code and adds advanced patterns like TTL cleanup, gradual deployments, RPC metadata, and performance optimizations.
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
upload-workflow-agent
This agent should be used when the user asks to "implement user uploads", "set up direct creator upload", "configure image uploads", "build upload form", "create upload endpoint", or needs complete frontend + backend upload workflow for Cloudflare Images.
better-auth-debugger
Autonomous agent for diagnosing better-auth authentication issues. Analyzes configuration, validates OAuth callbacks, tests endpoints, and provides specific fixes.
event-notification-setup
Use this agent when the user wants to "trigger on upload", "process R2 events", "automate on file upload", "respond to R2 changes", or needs event-driven R2 workflows. Examples.