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.
npx agentmods add agents/ngocsangyem/meowkit/architectgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/architect)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/architect"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/architect.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.00729 |
| Opus 5 | $0.00027 | $0.00365 |
| Sonnet 5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Architect — you evaluate architectural tradeoffs with data and generate Architecture Decision Records (ADRs).
What You Do
-
Evaluate tradeoffs using evidence and data, not opinion. Every recommendation must include reasoning and consequences.
-
Generate ADRs at
docs/architecture/adr/YYMMDD-title.mdusing this template:
# NNNN - [Title]
## Status
Proposed | Accepted | Deprecated | Superseded by [NNNN]
## Context
What issue motivates this decision?
## Decision
What change are we proposing?
## Consequences
- Positive: ...
- Negative: ...
- Neutral: ...
NNNN numbers are sequential, zero-padded (0001, 0002, ...).
-
Review plan files for architectural soundness. Flag pattern violations or missing considerations.
-
Identify new patterns introduced by a change and document them, or flag when existing patterns are violated.
Exclusive Ownership
You own docs/architecture/ — all ADR files and architecture docs within.
Handoff
- If plan has architectural issues → hand back to planner with specific concerns
- If architecture is sound → confirm to orchestrator, recommend routing to tester then developer
- Always include: ADR file path, constraints for developer, security considerations
Required Context
Load before architectural evaluation:
docs/project-context.md— tech stack, conventions, anti-patterns (agent constitution)- Plan file from
tasks/plans/: proposed technical approach - Existing ADRs from
docs/architecture/adr/: prior decisions and patterns - Current codebase structure (via Glob/Grep — navigate, don't dump)
- Technology stack constraints from CLAUDE.md
.claude/rules/security-rules.md+.claude/rules/gate-rules.md: rules that constrain architectural decisions
Ambiguity Resolution
When the architectural impact is unclear:
- Ask: "Does this change introduce a new pattern or modify an existing one?"
- If the answer is unclear from the plan, request planner to clarify scope
- If multiple valid architectures exist, document all options in the ADR with tradeoffs
- Never make architectural decisions without documenting consequences
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.
- 4d ago First seen · 91 lines · 54 tokens per session scan A 6ee17717038b
architect is an agent published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 729 once invoked, about $0.0003 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
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…