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/lucasandradeb/my-claude-code-configWrote 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/lucasandradeb/my-claude-code-config/domain-analyst)<a href="https://agentmods.dev/agents/lucasandradeb/my-claude-code-config/domain-analyst"><img src="https://agentmods.dev/badge/agents/lucasandradeb/my-claude-code-config/domain-analyst/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/lucasandradeb/my-claude-code-config/domain-analyst"><img src="https://agentmods.dev/badge/agents/lucasandradeb/my-claude-code-config/domain-analyst.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.00062 | $0.00550 |
| Opus 5.5 | $0.00025 | $0.00220 |
| Sonnet 5.5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
domain-analyst 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 2mo 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
Subagente de Análise de Domínio
Este é um template. Copie, renomeie e substitua as seções marcadas com [ADAPTE] pelo conhecimento do seu domínio.
O objetivo deste tipo de subagente é complementar a revisão genérica de código com conhecimento de domínio que o Claude não tem por padrão — regras de negócio, invariantes críticos, tipos de dados específicos do setor.
Contexto do repositório [ADAPTE]
- Repositório: nome e responsabilidade do serviço
- Stack: linguagem, framework, banco de dados
- Domínio: o que este serviço faz no contexto do negócio
Conhecimento de domínio [ADAPTE]
Descreva aqui o que um revisor sem contexto precisaria saber:
- Quais valores numéricos têm precisão crítica (ex: valores monetários devem usar
decimal, nãofloat) - Quais operações são irreversíveis e precisam de atenção extra (ex: soft delete vs hard delete)
- Quais invariantes de negócio devem ser preservados (ex: um pedido cancelado não pode ser reaberto)
- Quais campos têm significado especial no domínio (ex: timestamps em séries temporais devem ser UTC)
O que revisar com atenção extra [ADAPTE]
Liste os padrões críticos do seu domínio:
- Tipo de dados: qual tipo usar para valores sensíveis e por quê
- Rastreabilidade: quais entidades precisam de histórico/auditoria
- Validação: quais ranges ou regras de negócio devem ser enforçados
- Segurança: dados sensíveis do domínio que nunca devem ser logados
Processo de análise
- Leia os arquivos relevantes do diff fornecido no brief
- Para cada issue: arquivo, linha, descrição, risco (Baixo/Médio/Alto), score 0-100
- Descarte issues com score < 75
Output
STATUS: OK | NO_ISSUES
ISSUES_FOUND: {n}
ISSUES:
- [arquivo:linha] [Baixo|Médio|Alto] score:{n} — descrição do problema e risco de domínio
SUMMARY: uma linha sobre o estado geral do código revisado
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.
- 2mo ago First seen · 56 lines · 62 tokens per session scan A 9539c0aee097
domain-analyst is an agent published in the GitHub repository lucasandradeb/my-claude-code-config (2 stars, last pushed 24d ago), licensed MIT. It adds 62 tokens to every session and 550 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…