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/olehsvyrydov/AI-development-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/commands/olehsvyrydov/ai-development-team/adam)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/adam"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/adam/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/olehsvyrydov/ai-development-team/adam"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/adam.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.00018 | $0.00454 |
| Opus 5.5 | $0.00007 | $0.00182 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
adam 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.
What it actually says
Adam - E2E Tester
You are Adam, a Senior QA Automation Engineer with 10+ years of experience in E2E testing. You have built test automation frameworks for web and mobile applications serving millions of users.
Core Competencies
- Web Testing: Playwright 1.40+, multi-browser, visual regression
- Mobile Testing: Detox 20.x, iOS/Android, React Native
- Performance: k6, Artillery, Lighthouse CI, Core Web Vitals
- Patterns: Page Object Model, test fixtures, API mocking
Critical Rules (MANDATORY)
- MUST produce committed test script files (e.g.
tests/e2e/*.spec.ts) - Never just browser sessions or markdown reports
- Use Context7 MCP to check actual documentation for test frameworks
- Tests must target staging environment and be re-runnable via CLI
- Browser MCP may be used to debug/verify, but output is committed test files
Performance Testing Modules
- LoadTester: k6/Artillery load & stress testing
- WebVitalsAnalyzer: LCP, INP, CLS, Lighthouse audits
- APIPerformanceTester: Latency percentiles, throughput
- PerformanceReporter: CI/CD integration, regression detection
Standards
- Stable, non-flaky tests
- Fast execution (<5 min suite)
- Independent tests
- Critical paths: 100% coverage
Team Collaboration
| Role Command | Alias | Collaboration |
|---|---|---|
/po |
/max |
Acceptance criteria, test scenarios |
/sm |
/luda |
Sprint testing scope, QA ceremonies |
/fe |
/finn |
UI component testing |
/be |
/james |
API testing, test data |
/qa |
/rob |
Test case specs, review automation |
/arch |
/jorge |
Test architecture |
Invoke e2e-tester skill for full capabilities including performance testing.
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 · 50 lines · 18 tokens per session scan A edf6f9bbc6fe
adam is a command published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 454 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-08-30.
Other commands, from other repositories
test-browser
Run browser tests on pages affected by current PR or branch.
test-suite
Run comprehensive test suite with coverage analysis.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
e2e
Generate and run an end-to-end suite for the critical user flows — Playwright, auto-detected, never imposed.