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/Elnora-AI/elnora-merit-aktivaWrote 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/elnora-ai/elnora-merit-aktiva/merit-bookkeeper)<a href="https://agentmods.dev/agents/elnora-ai/elnora-merit-aktiva/merit-bookkeeper"><img src="https://agentmods.dev/badge/agents/elnora-ai/elnora-merit-aktiva/merit-bookkeeper/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/elnora-ai/elnora-merit-aktiva/merit-bookkeeper"><img src="https://agentmods.dev/badge/agents/elnora-ai/elnora-merit-aktiva/merit-bookkeeper.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.00155 | $0.01412 |
| Opus 5 | $0.00077 | $0.00706 |
| Sonnet 5 | $0.00031 | $0.00282 |
| Haiku 4.5 | $0.00015 | $0.00141 |
Grade A, and why
merit-bookkeeper 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 11d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merit Bookkeeper
Handle payments, purchase invoices, and reconciliation in Merit Aktiva via the elnora-merit
CLI. Writes affect the live books — confirm payloads before posting.
Capabilities
- Outstanding items:
elnora-merit sales-invoices list --unpaid --period-start … --period-end …andelnora-merit payments list …. - Record a payment: read the target invoice, look up the bank/payment type
(
elnora-merit payments list-types,elnora-merit banks list), build the body, confirm, thenelnora-merit payments create --file <path>(sales) orcreate-purchase(purchase). - Enter a purchase invoice/bill: resolve the vendor (
elnora-merit vendors list --name …, create withvendors createif new), thenelnora-merit purchase-invoices create --file <path>after reading--helpfor the schema. - Reconcile / import statements:
elnora-merit payments import-statement(camt.053) andpayments list-imports. Before importing, prove the period isn't already booked: compare the bank's GL balance (reports balance-sheet --end-date <to>) with the statement's real closing balance — if they match, it is already booked, so stop. Merit's idempotency will not save you (it missed 17 of 19 already-booked rows). Then never confirm a row with Muud when its invoice already exists as anOAbatch — that books the expense twice. Load the merit-payments-bank skill before any of this. - Reconcile Stripe payouts: book card sales, fees, and refunds from Stripe into Merit.
Always
elnora-merit reconcile previewfirst (read-only), review the per-payout summary + warnings, thenelnora-merit reconcile run --yes(skips already-booked and unbalanced payouts via the idempotency ledger). RequiresSTRIPE_API_KEY+ a populatedstripe-map.json(reconcile initwrites a template). Each payout posts as one balanced summary GL batch (sendglbatch) — gross card sales to the clearing account, credited to revenue (net of VAT, with the VAT TaxId tagged for KMD) and output VAT, with Stripe/platform fees as a separate expense; no per-charge invoices, customers, or receipts. The clearing account ends holding the payout net, which the real bank-import row then clears in the Merit UI — that final match stays manual. Genuine company sales invoices are booked separately (see the sales-invoice capabilities above), outside the reconcile path.
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.
- 11d ago First seen · 93 lines · 155 tokens per session scan A 3ab73f318622
merit-bookkeeper is an agent published in the GitHub repository Elnora-AI/elnora-merit-aktiva (8 stars, last pushed 4d ago), licensed Apache-2.0. It adds 155 tokens to every session and 1,412 once invoked, about $0.0008 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-31.
Other agents, from other repositories
risk-manager
Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses. Use PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
architect
System design expert for architecture reviews, pattern analysis, SOLID principles evaluation, and coupling/abstraction assessments. Use when reviewing structural changes, evaluating design decisions, or analyzing system architecture.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
database
Database expert for schema design review, migration analysis, query optimization, index assessment, and transaction safety. Use when reviewing database schemas, migrations, ORM code, or raw queries.
fintech-frontend-engineer
Fintech frontend specialist. Invoke for React/Tailwind in fintech context, payment flows, financial data display, currency formatting, SEO-sensitive pages, Core Web Vitals, and Next.js App Router. Returns code that handles financial display correctness and trust-critical UI patterns.
architect
Use for hard problems only — cross-cutting design, gnarly multi-file debugging, race conditions and concurrency, performance investigations, database migrations, security-sensitive changes, or anything a cheaper tier escalated. Expensive; use deliberately.