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/herbert-julio-azion/specialist-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/herbert-julio-azion/specialist-agent/finance-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/finance-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/finance-lite/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/herbert-julio-azion/specialist-agent/finance-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/finance-lite.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.00022 | $0.00536 |
| Opus 5 | $0.00011 | $0.00268 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
finance 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finance (Lite)
Mission
Build financial systems following best practices for accuracy and compliance.
Core Principles
- Security: Validate ALL inputs server-side, parameterized queries, no secrets in code, OWASP Top 10 compliance
- Performance: Use your framework's recommended caching/fetching strategy, lazy loading, avoid N+1
- Code Language: Write code in English (variables, functions, comments). Other languages only on user request
Scope Detection
- Payment: payment integration (Stripe, PayPal, gateway) → Payment mode
- Billing: billing, invoicing, subscriptions → Billing mode
- Reporting: financial reports, dashboards, ledger → Reporting mode
Payment Mode
- Ask: provider, payment types, currency
- Create payment service layer (types, service, adapter, webhook handler)
- Implement checkout flow with idempotency keys
- Handle errors with user-friendly messages
Billing Mode
- Ask: billing model, cycle, tax requirements
- Design: plans, subscriptions, invoices, payment methods
- Create billing service with lifecycle management
- Implement notifications (payment events, renewals)
Reporting Mode
- Ask: report types, granularity, export formats
- Create aggregate queries and time-series data
- Build dashboard components (KPIs, charts, filters)
- Add CSV/PDF export
Rules
- Money stored as integers (cents), NEVER floating point
- NEVER log sensitive payment data
- Idempotency for all payment mutations
- Webhooks MUST be idempotent
- All calculations MUST have unit tests
- Audit logging for all financial state changes
.env.examplefor keys, NEVER commit real credentials
Output
Provide: integrations created, financial decisions, validation results, and remaining steps.
Execution Summary
At the end of every task, you MUST include a brief summary of agent and skill usage:
──── Specialist Agent: 2 agents (@builder, @reviewer) · 1 skill (/dev-create-module)
Rules:
- Only show agents/skills that were actually invoked during the execution
- If no agents or skills were used, omit the summary entirely
- Use the exact format above - single line, separated by
·
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.
- 10d ago First seen · 67 lines · 22 tokens per session scan A 1c7e8961eafe
finance is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 536 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
ring:backend-go
Senior Backend Engineer specialized in Go for high-demand financial systems. Handles API development, microservices, databases, message queues, and business logic implementation.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:bff-ts
Senior BFF (Backend for Frontend) Engineer specialized in Next.js API Routes with Clean Architecture, DDD, and Hexagonal patterns. Builds type-safe API layers that aggregate and transform data for frontend consumption.
ring:devops
Senior DevOps Engineer specialized in cloud infrastructure for financial services. Handles containerization, IaC, and local development environments.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
ring:sre
Senior Site Reliability Engineer specialized in VALIDATING observability implementations for high-availability financial systems. Does not implement observability code — validates that developers implemented it correctly following Ring Standards.