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/TheBeardedBearSAS/claude-craftWrote 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-code-quality)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/check-code-quality"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-code-quality/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-code-quality"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-code-quality.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.00004 | $0.01448 |
| Opus 5.5 | $0.00002 | $0.00579 |
| Sonnet 5.5 | $0.00001 | $0.00290 |
| Haiku 4.5 | $0.00000 | $0.00145 |
Grade A, and why
check-code-quality 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Code Quality Analysis
Analyze code quality and identify areas for improvement in the Angular project.
What This Command Does
-
Code Quality Metrics
- TypeScript strict compliance
- ESLint violations
- Code complexity
- Duplicated code
-
Angular-Specific Quality
- Component best practices
- RxJS patterns
- Memory leak prevention
- Performance patterns
-
Generated Report
- Quality score
- Issues by severity
- Actionable recommendations
Quality Criteria
1. TypeScript Quality
// ✅ Good - Explicit types, null safety
interface User {
id: string;
name: string;
email: string | null;
}
function getUser(id: string): User | undefined {
return users.find(u => u.id === id);
}
const userName = getUser('1')?.name ?? 'Unknown';
// ❌ Bad - Implicit any, no null handling
function getUser(id) {
return users.find(u => u.id === id);
}
const userName = getUser('1').name; // Potential null error
2. Component Quality
// ✅ Good - Small, focused component
@Component({
selector: 'app-user-avatar',
standalone: true,
changeDetection: ChangeDetectionStrategy.OnPush,
template: `
<img [src]="avatarUrl()" [alt]="user().name" class="avatar" />
`
})
export class UserAvatarComponent {
user = input.required<User>();
avatarUrl = computed(() => this.user().avatar ?? '/default-avatar.png');
}
// ❌ Bad - Large component doing too much
@Component({
selector: 'app-user-page',
template: `<!-- 500 lines of HTML -->`
})
export class UserPageComponent {
// 50+ methods, multiple responsibilities
}
3. RxJS Best Practices
// ✅ Good - Proper subscription management
export class UserListComponent implements OnInit {
private destroyRef = inject(DestroyRef);
ngOnInit(): void {
this.userService.users$
.pipe(takeUntilDestroyed(this.destroyRef))
.subscribe(users => this.handleUsers(users));
}
}
// ❌ Bad - Memory leak (no unsubscribe)
export class UserListComponent implements OnInit {
ngOnInit(): void {
this.userService.users$.subscribe(users => {
this.users = users; // Never unsubscribed!
});
}
}
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 · 241 lines · 4 tokens per session scan A 17f88c9b902f
check-code-quality is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 7d ago), licensed MIT. It adds 4 tokens to every session and 1,448 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.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
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.
review
Trigger code review on recent changes.
checklist
Generate a custom checklist for the current feature based on user requirements.