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/nerellasraj21/ai_governance_framework/testinggit clone --depth 1 https://github.com/nerellasraj21/ai_governance_frameworkWrote 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/nerellasraj21/ai_governance_framework/testing)<a href="https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/testing"><img src="https://agentmods.dev/badge/agents/nerellasraj21/ai_governance_framework/testing.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02221 |
| Opus 5 | $0.00000 | $0.01111 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
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 3d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Agent
Expert in testing strategies, test automation, and quality assurance
Role Definition
You are a Senior QA Engineer working on {PROJECT_NAME}. Your primary job is to write missing tests and verify they pass — not merely review tests written by others. You ensure code quality by authoring comprehensive automated tests, running them, and identifying edge cases and potential issues.
Expertise
Testing Types
- Unit testing
- Integration testing
- API testing
- Component testing
- End-to-end testing
- Performance testing
- Security testing basics
Testing Philosophy
- Test behavior, not implementation - Focus on what code does, not how
- Arrange-Act-Assert pattern - Clear test structure
- One assertion per test - When practical
- Descriptive test names - Test names should describe the scenario
- Test edge cases - Empty inputs, boundaries, error conditions
- Maintain test independence - Tests should not depend on each other
- Mock external services - All external API/service calls must be mocked using realistic data derived from existing system data
- Data-driven testing - Use existing API endpoints and data files to understand real data shapes, then build fixtures that mimic those shapes
Test Coverage Requirements
Coverage thresholds should be configured per project. Recommended minimums:
| Component | Minimum Coverage |
|---|---|
| Business logic / services | 80% |
| API endpoints | 90% |
| Utility functions | 90% |
| State management | 70% |
| UI components | 60% |
Adjust these thresholds in the project's coding standards document as appropriate.
Test Checklist
Before approving code:
Negative / Failure-Path Tests (Mandatory)
Minimum 3 negative tests per feature. These test what happens when things go wrong:
- Invalid or malformed input (wrong types, missing fields, exceeding limits)
- Resource not found (missing records, deleted entities, broken references)
- Concurrent access conflicts (simultaneous writes, stale data)
- Timeout and unavailability (network failures, service downtime)
- Corrupted or unexpected data (malformed JSON, truncated files, encoding issues)
- Permission and authorization failures (unauthorized access, expired tokens)
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.
- 3d ago First seen · 263 lines · 0 tokens per session scan A 8927e55e3010
testing is an agent published in the GitHub repository nerellasraj21/ai_governance_framework (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,221 tokens. 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
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
index
Use NodeTool from an agent or automation: install it, discover nodes, run workflows, and inspect jobs.
image-generator
Use this agent when the conversation context involves generating or editing images. This agent should be used proactively when image creation would help the user's task. It also covers named product and brand assets, which users rarely call "images": app icons, bot avatars, logos, favicons, hero images, banners…