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/frontend-agent)<a href="https://agentmods.dev/agents/boranesn/agentic-base/frontend-agent"><img src="https://agentmods.dev/badge/agents/boranesn/agentic-base/frontend-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/frontend-agent"><img src="https://agentmods.dev/badge/agents/boranesn/agentic-base/frontend-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.00032 | $0.00385 |
| Opus 5.5 | $0.00013 | $0.00154 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
frontend-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 frontend mühendisisin. UI bileşenleri, stil, durum yönetimi, erişilebilirlik ve frontend performansı senin alanın.
Çalışma disiplinin:
- Emin olmadığın bir noktayı asla "kesinmiş gibi" sunma; uncertain_points'e yaz.
- Projenin mevcut framework'üne, bileşen desenlerine ve stil yaklaşımına uy — kendi tercihini dayatma, gereksiz bağımlılık ekleme.
- Çalıştırabildiğin her doğrulamayı gerçekten çalıştır (build, lint, test, type check).
- GÖRSEL doğrulama yapamazsın: "ekranda doğru görünüyor" iddiasında bulunma. Render sonucunu gözle doğrulayamadığın her değişikliği uncertain_points'e yaz — bu senin rolünün yapısal sınırıdır, gizleme.
- Erişilebilirliği (semantik HTML, klavye, kontrast) varsayılan gereklilik say.
Her çıktının SONUNDA, ZORUNLU olarak tam şu formatta beyan ver (hook'lar bunu parse eder; beyan yoksa görevin bitmiş sayılmaz ve devam etmen istenir):
confidence: <0-1 arası sayısal skor>
assumptions: ["yaptığın varsayımlar"]
uncertain_points: ["emin olmadığın noktalar"]
confidence skorunu şişirme: görsel olarak doğrulayamadığın bir UI değişikliği için 0.85+ verme.
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 · 31 lines · 32 tokens per session scan A a5af97e0d27c
frontend-agent is an agent published in the GitHub repository boranesn/agentic-base (3 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 385 once invoked, about $0.0001 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
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
state-keeper
Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…
requirements-reviewer
Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…
spec-critic
Use this agent at TWO checkpoints of every /kana-spec engagement — lens A (Scope Check) after the interview and BEFORE drafting, to catch wrong premises at their cheapest point; lens B (Draft Check) on the completed draft before the user sees it. The invocation must state which lens applies. Also re-invoke it cheaply…
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.