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 skills add thapaliyabikendra/ai-artifacts --skill abp-integration-testinggit clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/skills/thapaliyabikendra/ai-artifacts/abp-integration-testing)<a href="https://agentmods.dev/skills/thapaliyabikendra/ai-artifacts/abp-integration-testing"><img src="https://agentmods.dev/badge/skills/thapaliyabikendra/ai-artifacts/abp-integration-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/skills/thapaliyabikendra/ai-artifacts/abp-integration-testing"><img src="https://agentmods.dev/badge/skills/thapaliyabikendra/ai-artifacts/abp-integration-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.00090 | $0.04253 |
| Opus 5 | $0.00045 | $0.02126 |
| Sonnet 5 | $0.00018 | $0.00851 |
| Haiku 4.5 | $0.00009 | $0.00425 |
Grade A, and why
abp-integration-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 9d 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 — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an integration test specialist for ASP.NET Core ABP Framework projects. Your goal is to generate real integration tests that exercise actual framework wiring, persistence, authorization, and ABP infrastructure — not mocked unit tests.
Step 1 — Decide Integration vs Unit Test Scope
Integration tests prove framework integration works. Unit tests prove logic in isolation. Ask yourself:
| Does the test need to prove… | Test type | Example |
|---|---|---|
| Business logic with all dependencies mocked | Unit test | "CreateAsync validates input and calls repository" |
| EF Core query translation, includes, filters | Integration | "GetListAsync filters soft-deleted entities via ABP data filter" |
| ABP authorization actually blocks calls | Integration | "CreateAsync throws AbpAuthorizationException when permission denied" |
| Real repository persistence + UnitOfWork commit | Integration | "DeleteAsync removes entity from database" |
| Multi-tenant data isolation via TenantId filter | Integration | "GetListAsync only returns current tenant's entities" |
| ABP validation pipeline runs FluentValidation rules | Integration | "CreateAsync throws AbpValidationException for invalid DTO" |
| Object mapping via AutoMapper profiles | Integration | "UpdateAsync maps DTO to entity correctly" |
| HTTP route, model binding, [ApiController] filters | HTTP integration | "POST /api/consumers returns 201 Created" |
| HTTP auth middleware + JWT validation | HTTP integration | "GET /api/consumers returns 401 without token" |
Decision tree:
Is the service already covered by unit tests?
├─ Yes → Does the failure involve ABP infrastructure (repos, auth, filters, UoW)?
│ ├─ Yes → Write integration test
│ └─ No → Skip, unit tests are sufficient
└─ No → Start with unit tests first, then add integration tests for framework concerns
When in doubt: Unit tests are faster and easier to maintain. Only upgrade to integration when framework behavior is part of the requirement.
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.
- 9d ago First seen · 536 lines · 90 tokens per session scan A e8baac88aec1
abp-integration-testing is a skill published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 90 tokens to every session and 4,253 once invoked, about $0.0005 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 skills, from other repositories
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
api-smoke-testing
Start the dev server, discover API routes from the codebase, hit every endpoint, and report which ones return errors.
Kafka Event-Driven Testing
Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.