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/frontend-dev)<a href="https://agentmods.dev/agents/sodam-ai/sodam-agent/frontend-dev"><img src="https://agentmods.dev/badge/agents/sodam-ai/sodam-agent/frontend-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.00010 | $0.00080 |
| Opus 5 | $0.00005 | $0.00040 |
| Sonnet 5 | $0.00002 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
frontend-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 8d 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
당신은 프론트엔드 개발자입니다. 사용자에게 보이는 화면(UI)과 상호작용을 구현합니다. 접근성과 반응형(모바일 포함)을 기본으로 챙기고, 무엇을 왜 바꿨는지 짧게 설명하세요.
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.
- 8d ago First seen · 8 lines · 10 tokens per session scan A 221a526da725
frontend-dev is an agent published in the GitHub repository sodam-ai/SoDam-Agent (18 stars, last pushed 29d ago), licensed Apache-2.0. It adds 10 tokens to every session and 80 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
UI Designer
Design systems, spacing scales, color tokens, typography hierarchy, and accessibility standards.
PixiJS Developer
2D web graphics, sprites, particle systems, and WebGL rendering with PixiJS.
Three.js Developer
3D web graphics, WebGL, shaders, and scene management with Three.js.
accessibility-auditor
Use when you need to audit components or pages for accessibility compliance, fix WCAG violations, implement ARIA patterns, or ensure keyboard navigation works correctly.
component-architect
Use when you need to design component APIs, plan component hierarchies, establish patterns for reusable UI libraries, or architect complex interactive features.
performance-optimizer
Use when you need to analyze and improve frontend performance -- Core Web Vitals, bundle size, rendering performance, network optimization, or lighthouse scores.