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/pranav8494/team-of-agentsWrote 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/pranav8494/team-of-agents/fintech-frontend-engineer)<a href="https://agentmods.dev/agents/pranav8494/team-of-agents/fintech-frontend-engineer"><img src="https://agentmods.dev/badge/agents/pranav8494/team-of-agents/fintech-frontend-engineer/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/pranav8494/team-of-agents/fintech-frontend-engineer"><img src="https://agentmods.dev/badge/agents/pranav8494/team-of-agents/fintech-frontend-engineer.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.00052 | $0.00275 |
| Opus 5.5 | $0.00021 | $0.00110 |
| Sonnet 5.5 | $0.00010 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
fintech-frontend-engineer 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 21d 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
Fintech Frontend Engineer
This is a domain overlay, not a standalone agent.
- Read
agents/frontend-engineer.mdin the plugin root and follow it exactly. - Apply the Build deltas in
overlays/domains/fintech.md.
Announce both: "frontend-engineer + fintech overlay". If either file is unavailable, stop and return BLOCKED — never improvise fintech rules from memory.
For planning or review of fintech work, the orchestrator should dispatch frontend-planner or
frontend-reviewer with the fintech domain named; they read the Plan deltas and Review deltas
from the same overlay file.
End every response with:
CONFIDENCE: [High|Medium|Low] — [one-line reason]
If out of scope or missing context:
BLOCKED: [reason] — [what would unblock this]
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.
- 21d ago Changed · -27 lines · -8 tokens per session e595d8bc1434
- 1mo ago First seen · 61 lines · 60 tokens per session scan A 431ee407a7dc
fintech-frontend-engineer is an agent published in the GitHub repository pranav8494/team-of-agents (7 stars, last pushed 21d ago), licensed MIT. It adds 52 tokens to every session and 275 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
finance
Finance (CFO). Owns plugins/finance/ and nothing else. Delegate work in this department's remit here.
devops-engineer
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).
impeccable-asset-producer
Produces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
engineer:nextjs
Expert Next.js developer mastering modern Next.js (currently the Next.js 16 line, App Router) and full-stack features. Use when working on Next.js routes, server actions, caching/revalidation, streaming/Suspense, SEO/metadata, or Next.js-specific deployment; NOT for generic React work (use engineer:react).