check-testing

check-testing is a command for Claude Code from TheBeardedBearSAS/claude-craft. It costs 6 tokens per session (1,825 once invoked), scanned A, original, MIT.

An Angular project command that reviews test coverage and the quality of automated tests.

In plain words
What is it for?
Use it to inspect line, branch, function, and statement coverage and produce a report with recommendations.
Why use it?
It shows where tests are missing and highlights issues in test structure, mocks, asynchronous code, and edge cases.

Command for Claude Code

Part of the claude-craft plugin — 56 skills, 94 commands, 47 agents, 5 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/thebeardedbearsas/claude-craft/check-testing
Clone the repo
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 56 skills, 94 commands, 47 agents, 5 hooks.

Wrote 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.

agentmods badge for check-testing

README.md
[![agentmods](https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-testing.svg)](https://agentmods.dev/commands/thebeardedbearsas/claude-craft/check-testing)
Your own site
<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/check-testing"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,825 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.01825
Opus 5 $0.00003 $0.00912
Sonnet 5 $0.00001 $0.00365
Haiku 4.5 $0.00001 $0.00183

Measured 5d ago against content hash 9c4ed4050929, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-testing 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 5d 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.

.claude/commands/angular/check-testing.md · 295 lines

How it starts

The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Angular Test Coverage and Quality Analysis

Analyze test coverage and quality in the Angular project.

What This Command Does

  1. Coverage Analysis

    • Line coverage
    • Branch coverage
    • Function coverage
    • Statement coverage
  2. Test Quality

    • Test patterns (AAA)
    • Mock usage
    • Async handling
    • Edge case coverage
  3. Generated Report

    • Coverage metrics
    • Missing tests
    • Quality recommendations

Testing Standards

1. Component Testing

// ✅ Good - Comprehensive component test
describe('UserCardComponent', () => {
  let fixture: ComponentFixture<UserCardComponent>;
  let component: UserCardComponent;

  beforeEach(async () => {
    await TestBed.configureTestingModule({
      imports: [UserCardComponent]
    }).compileComponents();

    fixture = TestBed.createComponent(UserCardComponent);
    component = fixture.componentInstance;
  });

  describe('rendering', () => {
    it('should display user name', () => {
      // Arrange
      const user = { id: '1', name: 'John Doe', email: '[email protected]' };

      // Act
      fixture.componentRef.setInput('user', user);
      fixture.detectChanges();

      // Assert
      expect(fixture.nativeElement.textContent).toContain('John Doe');
    });

    it('should show loading state', () => {
      fixture.componentRef.setInput('loading', true);
      fixture.detectChanges();

      expect(fixture.nativeElement.querySelector('.loading')).toBeTruthy();
    });
  });

  describe('interactions', () => {
    it('should emit selected event on click', () => {
      // Arrange
      const user = { id: '1', name: 'John' };
      fixture.componentRef.setInput('user', user);
      fixture.detectChanges();

      const spy = vi.fn();
      component.selected.subscribe(spy);

      // Act
      fixture.nativeElement.querySelector('button').click();

      // Assert
      expect(spy).toHaveBeenCalledWith('1');
    });
  });
});

2. Service Testing

// ✅ Good - Service test with mocked HTTP
describe('UsersApiService', () => {
  let service: UsersApiService;
  let httpMock: HttpTestingController;

  beforeEach(() => {
    TestBed.configureTestingModule({
      providers: [
        UsersApiService,
        provideHttpClient(),
        provideHttpClientTesting()
      ]
    });

    service = TestBed.inject(UsersApiService);
    httpMock = TestBed.inject(HttpTestingController);
  });

  afterEach(() => {
    httpMock.verify(); // Verify no outstanding requests
  });

  describe('getUsers', () => {
    it('should return users list', () => {
      const mockUsers = [{ id: '1', name: 'John' }];

      service.getUsers().subscribe(users => {
        expect(users).toEqual(mockUsers);
      });

      const req = httpMock.expectOne('/api/users');
      expect(req.request.method).toBe('GET');
      req.flush(mockUsers);
    });

    it('should handle error', () => {
      service.getUsers().subscribe({
        error: err => expect(err.status).toBe(500)
      });

      const req = httpMock.expectOne('/api/users');
      req.flush('Error', { status: 500, statusText: 'Server Error' });
    });
  });
});

Read the full file on GitHub · 295 lines

Changes

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.

  1. 5d ago First seen · 295 lines · 6 tokens per session scan A 9c4ed4050929

Subscribe to this mod's changes

check-testing is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 1,825 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.