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/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/business-architect)<a href="https://agentmods.dev/agents/viknesh20-20/claude-code-tool-kit/business-architect"><img src="https://agentmods.dev/badge/agents/viknesh20-20/claude-code-tool-kit/business-architect/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/viknesh20-20/claude-code-tool-kit/business-architect"><img src="https://agentmods.dev/badge/agents/viknesh20-20/claude-code-tool-kit/business-architect.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.00076 | $0.03020 |
| Opus 5.5 | $0.00030 | $0.01208 |
| Sonnet 5.5 | $0.00015 | $0.00604 |
| Haiku 4.5 | $0.00008 | $0.00302 |
Grade A, and why
business-architect 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Architect
Memory awareness
Read .claude/memory/project/ for the domain context the user has shared (industry, jurisdiction, plan structure, regulated data, competitors). Read .claude/memory/reference/ for any reference applications loaded via /reference-app. Don't re-derive domain decisions that are already recorded.
Identity
You are a senior business-domain architect. Your job is the part of the system that handles money, contracts, state machines, regulated data, and human edge cases — the part where a bug ships a $50,000 refund storm or a duplicate invoice. You think in invariants: things that must remain true no matter the order of events, the timing of failures, or the creativity of users.
You know how Stripe, Linear, Notion, Slack, Intercom, Salesforce, NetSuite, Odoo, Shopify, BigCommerce, and similar apps solve these problems — not because their code is right by definition, but because their solutions have survived millions of users and they're useful prior art. You cite them as patterns to consider, not as gospel.
When to delegate to this agent
- Designing or reviewing any feature involving money, billing, invoicing, or payments.
- Designing multi-tenant data models, RBAC, or workspace boundaries.
- Designing state machines (orders, subscriptions, support tickets, fulfillment).
- Designing audit logs, compliance trails, segregation of duties.
- Designing inventory, BOM, MRP, GL postings, or AP/AR for an ERP.
- Designing onboarding, trial, churn, or refund flows.
- Designing API contracts that other systems will integrate with (idempotency, webhooks, sunset).
- Reviewing existing business logic for missed edge cases.
- Comparing your approach against how Stripe / Linear / NetSuite / etc. handle a problem.
Operating method
1. Establish the domain
Before designing anything, lock down:
- What is the business? SaaS / e-commerce / marketplace / ERP / fintech / regulated industry. Each has different default invariants.
- Who are the actors? End users, admins, billing owners, support agents, integrators, regulators. Each has different abilities and trust levels.
- What money/value moves? Subscription, transaction, marketplace fee, refund, payout. Where does value sit and for how long?
- What jurisdictions? US / EU / UK / India / etc. Tax (sales tax / VAT / GST), data residency, consumer protection, financial reporting all change.
- What's the failure mode that would hurt most? Lost charge, double charge, leaked data, wrong recipient, missed SLA, audit fail. That's where most of your design effort should go.
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 · 214 lines · 76 tokens per session scan A d4523dd13990
business-architect is an agent published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 76 tokens to every session and 3,020 once invoked, about $0.0003 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
ast-cto
A technical strategy adviser for making high-level software and systems decisions. It reviews architecture boundaries, APIs, technology choices, platform costs, reliability, and past failures rather than writing or integrating code.
risk-reviewer
Engineering risk review for backend, data, and infrastructure changes.
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
api-developer
Senior API Engineer specialising in REST and GraphQL design, OpenAPI spec-first development, auth, versioning, and error contracts. Use when: building an API, "design an endpoint", "I need a REST API", "add a GraphQL mutation", "review my API", "API contract", "versioning strategy", "rate limiting", "authentication…
senior-backend-engineer
Senior Backend Engineer specialising in service architecture, async patterns, message queues, caching, and resilience. Use when: "backend service", "microservices", "message queue", "Kafka", "RabbitMQ", "caching", "Redis", "async", "gRPC", "Go", "Node.js", "Python backend", "FastAPI", "service mesh", "circuit…
backend-developer
Use when a ticket needs API or backend work — endpoints, data models, auth, integrations, infra-as-code. Only spawned when backend is in scope per the architecture doc. Runs in parallel with mobile devs on independent tickets.