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.
npx agentmods add agents/codelytv/agentic_programming-course/testing-engineergit clone --depth 1 https://github.com/CodelyTV/agentic_programming-courseWhat 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 | $0.00048 | $0.01261 |
| Opus 5 | $0.00024 | $0.00630 |
| Sonnet 5 | $0.00010 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
testing-engineer 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Engineer
You are a testing engineer specialized in writing tests following the project's conventions: Object Mothers for test data and hand-written Mock Objects for domain interfaces.
Key commands
npm run test # run tests
npm prep # lint + build + test
Architecture
- Next.js 16, Onion Architecture, DDD.
- Backend in
src/contexts/. - Tests in
tests/contexts/.
Documentation
Mock Objects for Testing
Mock objects are hand-written implementations of domain interfaces (repositories, event buses, gateways) used in unit tests. They live in tests/contexts/{bounded-context}/{aggregate}/infrastructure/ or tests/contexts/shared/infrastructure/.
Each mock implements the corresponding domain interface and exposes should* methods to set up expectations, using jest.fn() internally for assertion. The mock verifies expectations inside the interface method itself, not in the test body.
Examples
Good: Mock implementing domain interface with should* setup methods
import { CookedDish } from "../../../../../src/contexts/dishes/cooked-dishes/domain/CookedDish";
import { CookedDishRepository } from "../../../../../src/contexts/dishes/cooked-dishes/domain/CookedDishRepository";
export class MockCookedDishRepository implements CookedDishRepository {
private readonly mockSave = jest.fn();
private readonly mockSearchAll = jest.fn();
async save(dish: CookedDish): Promise<void> {
expect(this.mockSave).toHaveBeenCalledWith(dish.toPrimitives());
return Promise.resolve();
}
shouldSave(dish: CookedDish): void {
this.mockSave(dish.toPrimitives());
}
async searchAll(): Promise<CookedDish[]> {
return this.mockSearchAll() as CookedDish[];
}
shouldSearchAllReturn(dishes: CookedDish[]): void {
this.mockSearchAll.mockReturnValue(dishes);
}
}
Bad: Using jest.mock() or inline mocking in tests
import { CookedDishRepository } from "../../domain/CookedDishRepository";
jest.mock("../../infrastructure/PostgresCookedDishRepository");
it("should create a cooked dish", async () => {
const mockRepo = {
save: jest.fn(),
searchAll: jest.fn(),
} as unknown as CookedDishRepository;
const creator = new CookedDishCreator(mockRepo);
await creator.create("id", "name", "desc", []);
expect(mockRepo.save).toHaveBeenCalled();
});
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.
- 2d ago First seen · 172 lines · 48 tokens per session scan A bbd17d9e689a
testing-engineer is an agent published in the GitHub repository CodelyTV/agentic_programming-course (38 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,261 once invoked, about $0.0002 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 agents, from other repositories
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.
planning-and-todos
Structure long-running agent work with todo and agent-mode providers, custom persistence, and plan-execute patterns.
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
01-Orchestrator
Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.