A project guide for testing and code quality with Jest, React Testing Library, Supertest, MongoDB, PostgreSQL, and ESLint. Jest runs tests, while ESLint checks code for common problems and style issues.

Use it to write or fix frontend, backend, unit, integration, and API tests, run test coverage, or resolve linting issues.

It gives the agent the project's expected testing and linting patterns instead of making it guess. It also separates tests that use temporary in-memory databases from tests that need real services.

testing — Skill for Claude Code and Codex by Team-Commonly/commonly

About the project

Commonly is a self-hosted collaborative workspace where people work with multiple AI agents, each retaining its own name, memory, skills, and workstation. Teams use it to assign and refine real work across different agent runtimes, and the catalogue entries supply agents, skills, and instructions for use in those rooms.

Team-Commonly/commonly · 1,370 stars · on GitHub · commonly.me

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/Team-Commonly/commonly

agentmods

npx agentmods add skills/team-commonly/commonly/testing

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/team-commonly/commonly/testing/github.svg)](https://agentmods.dev/skills/team-commonly/commonly/testing)

Your own site

<a href="https://agentmods.dev/skills/team-commonly/commonly/testing"><img src="https://agentmods.dev/badge/skills/team-commonly/commonly/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/team-commonly/commonly/testing"><img src="https://agentmods.dev/badge/skills/team-commonly/commonly/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,017 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.02017
Opus 5.5	$0.00012	$0.00807
Sonnet 5.5	$0.00006	$0.00403
Haiku 4.5	$0.00003	$0.00202

Measured today against content hash 74c20ae9c16a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

testing scanned grade A with 1 finding 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 today.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

axios.get.mockResolvedValue({ data: mockMessages });

fleet-skills/testing/SKILL.md · 243 lines

How it starts

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

Testing & Quality

Technologies: Jest, React Testing Library, Supertest, ESLint

Required Knowledge

Jest test framework
React Testing Library patterns
API testing with Supertest
In-memory database testing (MongoDB Memory Server, pg-mem)
ESLint configuration
Test-driven development

Relevant Documentation

Document	Topics Covered
`docs/development/LINTING.md`	ESLint setup, auto-fix, IDE integration
`docs/development/BACKEND.md`	Backend testing patterns
`docs/development/FRONTEND.md`	Frontend testing patterns

Testing Commands

# Unit tests (in-memory DBs — no services needed, default)
cd backend && npm test
cd backend && npm run test:coverage
./dev.sh test                        # same, runs inside Docker container

# Integration tests (real Docker Compose services)
./dev.sh up                          # start mongo + postgres first
./dev.sh test:integration            # INTEGRATION_TEST=true npm test --forceExit
# or manually:
INTEGRATION_TEST=true npm --prefix backend test -- --forceExit

# Frontend tests
cd frontend && npm test
cd frontend && npm run test:coverage

# Linting
npm run lint
npm run lint:fix

INTEGRATION_TEST env var

backend/__tests__/setup.js switches between two modes:

INTEGRATION_TEST not set (default): sets PG_HOST=undefined and MONGO_URI=undefined → triggers in-memory MongoDB Memory Server + pg-mem
INTEGRATION_TEST=true: connects to real services:
- MongoDB: localhost:27017 (db: commonly-test)
- PostgreSQL: localhost:5432 (db: commonly-test, user: postgres, no SSL)
- Requires ./dev.sh up to be running first

Override connection strings via env vars: MONGO_URI, PG_HOST, PG_PORT, PG_DATABASE, PG_USER, PG_PASSWORD.

High-value Current Test Areas

E2E Integration Tests

Two-Way Integration E2E: backend/__tests__/service/two-way-integration-e2e.test.js (23 tests)
- Inbound flow: External platforms (GroupMe, Discord) → Commonly via ingest endpoint
- Scheduler summarization: Buffer processing and agent event queuing
- Agent posting: commonly-bot posting summaries to pods via runtime API
- Outbound flow: Commonly → Discord webhooks / GroupMe bot API
- Full round-trip: External → Commonly → External
- Multi-agent: Clawdbot, custom agents, agent chaining
Integrations E2E: backend/__tests__/service/integrations-e2e.test.js
Clawdbot E2E: backend/__tests__/service/clawdbot-e2e.test.js

Read the full file on GitHub · 243 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.

today First seen · 243 lines · 31 tokens per session scan A 74c20ae9c16a

Subscribe to this mod's changes

testing is a skill published in the GitHub repository Team-Commonly/commonly (1,370 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 2,017 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-24.

Backend and APIs LLM Multi-Agent Testing Unit testing agent-protocol ai-agents open-source self-hosted

architecture-patterns

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…

yonatangross/orchestkit · 56 tokens

testing