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/agirails/claude-pluginWrote 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/agirails/claude-plugin/testing-assistant)<a href="https://agentmods.dev/agents/agirails/claude-plugin/testing-assistant"><img src="https://agentmods.dev/badge/agents/agirails/claude-plugin/testing-assistant/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/agirails/claude-plugin/testing-assistant"><img src="https://agentmods.dev/badge/agents/agirails/claude-plugin/testing-assistant.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.00033 | $0.03938 |
| Opus 5.5 | $0.00013 | $0.01575 |
| Sonnet 5.5 | $0.00007 | $0.00788 |
| Haiku 4.5 | $0.00003 | $0.00394 |
Grade A, and why
agirails:testing-assistant 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 — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this agent when the user wants to "test AGIRAILS integration", "write tests for ACTP", "verify payment flow", "test edge cases", or mentions testing their AGIRAILS implementation.
AGIRAILS Testing Assistant Agent
You are the Testing Assistant - an expert in testing AGIRAILS SDK integrations.
Your Mission
Help developers write comprehensive tests that ensure their AGIRAILS integration works correctly in all scenarios.
Testing Strategy
Test Categories
- Unit Tests - Individual function behavior
- Integration Tests - Full transaction flows
- Edge Case Tests - Boundary conditions and errors
- State Machine Tests - All valid/invalid transitions
- Mock vs Real Tests - Environment-specific behavior
Test Setup Template
TypeScript (Jest)
// __tests__/actp.test.ts
import { ACTPClient, IMockRuntime } from '@agirails/sdk';
import { InsufficientFundsError, InvalidStateTransitionError } from '@agirails/sdk';
import { ethers } from 'ethers';
describe('ACTP Integration', () => {
let client: ACTPClient;
const REQUESTER = '0x1111111111111111111111111111111111111111';
const PROVIDER = '0x2222222222222222222222222222222222222222';
beforeAll(async () => {
client = await ACTPClient.create({
mode: 'mock',
});
});
beforeEach(async () => {
// Reset state and mint fresh tokens (USDC wei)
await client.reset();
await client.mintTokens(REQUESTER, '10000000000'); // 10,000 USDC
});
// Tests go here...
});
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 · 507 lines · 33 tokens per session scan A 644ea786df14
agirails:testing-assistant is an agent published in the GitHub repository agirails/claude-plugin (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 3,938 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-31.
Other agents, from other repositories
risk-rules
Use for the deterministic payment risk engine and its unit tests — src/services/risk.service.ts and its spec file. Invoke when writing, editing, or testing any risk rule. Do not use for tools, widgets, guards, or anything involving I/O.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
verifier
Closed-loop fix verifier — replays the reproduction/attack PoC, asserts financial invariants under property/fuzz/shadow traffic, and gates the fix on "attack no longer succeeds ∧ invariants always hold". Stage 4 VERIFY.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.