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-security)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/check-security"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-security.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.1 | $0.00003 | $0.01512 |
| Opus 5 | $0.00002 | $0.00756 |
| Sonnet 5 | $0.00001 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
check-security 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 7d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Security Audit
Perform a comprehensive security audit of the Angular application.
What This Command Does
-
Vulnerability Scanning
- XSS vulnerabilities
- CSRF protection
- Injection risks
- Authentication issues
-
Dependency Audit
- npm audit results
- Outdated packages
- Known vulnerabilities
-
Generated Report
- Security score
- Vulnerabilities by severity
- Remediation steps
Security Checks
1. XSS Protection
// ✅ Safe - Angular sanitizes automatically
@Component({
template: `<div [innerHTML]="content"></div>`
})
export class SafeComponent {
content = '<p>Safe content</p>'; // Sanitized by Angular
}
// ❌ Dangerous - Bypassing sanitization
@Component({
template: `<div [innerHTML]="trustedContent"></div>`
})
export class DangerousComponent {
trustedContent = this.sanitizer.bypassSecurityTrustHtml(userInput);
// Only bypass for trusted sources!
}
2. CSRF Protection
// ✅ Good - XSRF protection enabled
// app.config.ts
export const appConfig = {
providers: [
provideHttpClient(
withXsrfConfiguration({
cookieName: 'XSRF-TOKEN',
headerName: 'X-XSRF-TOKEN'
})
)
]
};
// ❌ Bad - No CSRF protection
export const appConfig = {
providers: [
provideHttpClient() // No XSRF configuration
]
};
3. Authentication Security
// ✅ Good - Secure token handling
@Injectable({ providedIn: 'root' })
export class AuthService {
// Use sessionStorage (not localStorage) for tokens
private getToken(): string | null {
return sessionStorage.getItem('token');
}
// Check token expiration
isTokenValid(): boolean {
const token = this.getToken();
if (!token) return false;
try {
const payload = JSON.parse(atob(token.split('.')[1]));
return payload.exp * 1000 > Date.now();
} catch {
return false;
}
}
}
// ❌ Bad - Insecure token storage
localStorage.setItem('token', token); // Vulnerable to XSS
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.
- 7d ago First seen · 266 lines · 3 tokens per session scan A 63ac637de3bc
check-security is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 3 tokens to every session and 1,512 once invoked, about $0.0000 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 commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
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.