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 commands/ngocsangyem/meowkit/archgit 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/commands/ngocsangyem/meowkit/arch)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/arch"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/arch.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.00000 | $0.00463 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
arch 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 3d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/arch — Architecture Decision Records
Usage
/arch new [title]
/arch list
/arch review [number]
/arch impact [change description]
Behavior
Architecture as a first-class concern. Manages Architecture Decision Records (ADRs) and analyzes architectural impact of proposed changes.
Modes
/arch new [title]
Generate a new ADR using the architect agent.
- Assign the next sequential ADR number.
- Gather context: What decision needs to be made? What are the constraints? What options exist?
- Generate ADR with sections: Title, Status (Proposed), Context, Decision, Consequences, Alternatives Considered.
- Write to
docs/architecture/adr/YYMMDD-title.md. - Print summary and ask for review.
/arch list
List all ADRs with their current status.
- Scan
docs/architecture/adr/directory. - Print table:
# | Title | Status 1 | Use PostgreSQL for persistence | Accepted 2 | Event-driven architecture | Proposed 3 | Monorepo structure | Superseded by #5
/arch review [number]
Review and update an existing ADR.
- Read the specified ADR.
- Evaluate: Is the decision still valid? Has context changed? Are there new alternatives?
- Update status if needed: Proposed → Accepted, Accepted → Deprecated, Accepted → Superseded by #N.
- Add review notes with date.
/arch impact [change description]
Analyze the architectural impact of a proposed change.
- Parse the change description.
- Identify which architectural decisions (ADRs) are affected.
- Identify which system boundaries are crossed.
- Assess: Does this change align with existing ADRs or conflict with them?
- Print impact assessment: affected components, affected ADRs, risk level, recommendation.
Output
- For
new: ADR file atdocs/architecture/adr/YYMMDD-title.md - For
list: table of all ADRs - For
review: updated ADR file - For
impact: printed impact assessment with affected components and recommendations
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.
- 3d ago First seen · 66 lines · 0 tokens per session scan A 07e047aba717
arch is a command published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 463 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.