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/bdfinst/agentic-dev-teamWrote 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/agents/bdfinst/agentic-dev-team/angular-testing)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/angular-testing"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/angular-testing/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/agents/bdfinst/agentic-dev-team/angular-testing"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/angular-testing.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.00028 | $0.00513 |
| Opus 5.5 | $0.00011 | $0.00205 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
angular-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 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Testing
Output JSON:
{"status": "pass|warn|fail|skip", "issues": [{"severity": "error|warning|suggestion", "confidence": "high|medium|none", "file": "", "line": 0, "message": "", "suggestedFix": ""}], "summary": ""}
Status: pass=good Angular testing, warn=anti-patterns, fail=unreliable tests Severity: error=test won't catch regressions, warning=anti-pattern, suggestion=improvement Confidence: high=mechanical (use harness, fix TestBed); medium=test design; none=domain context
Context needs: full-file
File scope: *.spec.ts
Activates when
@angular/core in package.json dependencies.
Skip
Return skip when no .spec.ts files for Angular components/services in the changeset.
Detect
TestBed setup:
- Over-configured TestBed (importing entire modules instead of declaring only what's needed)
- Missing
TestBed.compileComponents()for components with external templates - Not resetting TestBed between tests when configuration changes
Component harnesses:
- Direct DOM queries (
querySelector,nativeElement) instead ofHarnessPredicate - Missing Material component harnesses when
@angular/materialis used - Not using
TestbedHarnessEnvironment.loader(fixture)for harness access
OnPush change detection:
- Tests that pass with Default but fail with OnPush (missing
fixture.detectChanges()) - Missing
ChangeDetectorRef.markForCheck()after programmatic state changes - Not wrapping async operations that update state
RxJS testing:
- Testing observables with
subscribe+donecallback instead of marble testing - Missing
fakeAsync/tickfor time-dependent observables - Not unsubscribing in
afterEach(subscription leaks) - Using real timers instead of
TestScheduler
HTTP testing:
- Mocking
HttpClientdirectly instead of usingHttpClientTestingModule - Not verifying outstanding requests with
httpTestingController.verify() - Missing error response testing
Ignore
Non-Angular tests, E2E tests (Protractor/Cypress), service worker tests.
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 · 67 lines · 28 tokens per session scan A bfa51b8aa10e
angular-testing is an agent published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 513 once invoked, about $0.0001 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-09-05.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.