Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftnpx agentmods add commands/thebeardedbearsas/claude-craft/check-architectureWrote 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/thebeardedbearsas/claude-craft/check-architecture)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/check-architecture"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-architecture/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/commands/thebeardedbearsas/claude-craft/check-architecture"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-architecture.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.00003 | $0.01559 |
| Opus 5.5 | $0.00001 | $0.00624 |
| Sonnet 5.5 | $0.00001 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
check-architecture 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Architecture Review
Analyze the Angular project architecture and provide recommendations for improvement.
What This Command Does
-
Structure Analysis
- Folder organization
- Feature modularity
- Dependency flow
- Layer separation
-
Pattern Verification
- Smart/Dumb components
- Service patterns
- State management
- Routing structure
-
Generated Report
- Architecture score
- Violations found
- Improvement recommendations
Architecture Standards
1. Folder Structure
✅ Expected Structure:
src/app/
├── core/ # Singleton services, guards, interceptors
│ ├── services/
│ ├── guards/
│ ├── interceptors/
│ └── models/
├── shared/ # Reusable components, pipes, directives
│ ├── components/
│ ├── pipes/
│ ├── directives/
│ └── validators/
├── features/ # Business features
│ └── {feature}/
│ ├── components/
│ ├── services/
│ ├── store/
│ └── {feature}.routes.ts
├── layout/ # Layout components
│ ├── header/
│ ├── sidebar/
│ └── shell/
├── app.config.ts
├── app.component.ts
└── app.routes.ts
2. Dependency Rules
✅ Allowed Dependencies:
- features → core, shared
- shared → core (types only)
- core → (external only)
❌ Forbidden Dependencies:
- core → features
- core → shared (components)
- shared → features
- features → features (cross-feature)
3. Smart/Dumb Pattern
// ✅ Container (Smart) Component
// - Injects services
// - Manages state
// - Handles side effects
@Component({
selector: 'app-user-list-container',
template: `
<app-user-list
[users]="users()"
[loading]="loading()"
(userSelected)="onSelect($event)"
/>
`
})
export class UserListContainerComponent {
private usersService = inject(UsersService);
users = this.usersService.users;
loading = this.usersService.loading;
}
// ✅ Presenter (Dumb) Component
// - Only @Input/@Output
// - No service injection
// - Pure display logic
@Component({
selector: 'app-user-list',
changeDetection: ChangeDetectionStrategy.OnPush
})
export class UserListComponent {
@Input({ required: true }) users!: User[];
@Input() loading = false;
@Output() userSelected = new EventEmitter<string>();
}
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 · 264 lines · 3 tokens per session scan A 7168057494d4
check-architecture is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed yesterday), licensed MIT. It adds 3 tokens to every session and 1,559 once invoked, about $0.0000 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-30.
Other commands, from other repositories
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
review-code
Trigger a comprehensive code review on recent changes or specified files.
clean-branches
Command "clean-branches" from qdhenry/Claude-Command-Suite, covering clean branches command, instructions, clean up all merged branches except protected ones, interactive cleanup with confirmation and batch delete remote branches.
README
Welcome to the Claude Command Suite! This collection of commands is organized into logical namespaces to help you quickly find the right tool for your task.
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.