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/atebites-hub/pjtemplate/testing_guidelines_templategit clone --depth 1 https://github.com/atebites-hub/PJTemplateWhat 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.01542 |
| Opus 5 | $0.00000 | $0.00771 |
| Sonnet 5 | $0.00000 | $0.00308 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
testing_guidelines_template 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 yesterday.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Guidelines Template
This document defines testing strategy and test-quality standards for [Project Name]. Tests are the executable safety net for refactoring, deployment confidence, and regression prevention.
Guidelines for Filling Out This Template
- Replace [Project Name] with your project's name.
- Select frameworks and tools that match your language and CI/CD.
- Set explicit coverage and reliability thresholds.
- Define required checks for local development and CI.
- Keep this file as the source of truth for test architecture and test-code quality.
- Reference repo structure: Store this in
/docs/agents/testing_guidelines.md.
Document Ownership and Overlap Rules
To keep standards clear:
- This document owns:
- Test strategy (unit/integration/e2e/security/performance)
- Test-code quality conventions
- Test execution and CI gating
coding_standards.mdowns production-code behavior standards.documentation_guidelines.mdowns/docs/tests/maintenance and documentation policy.AGENTS.mdowns project-level completion gates.
If overlap appears, keep normative testing detail here and cross-reference elsewhere.
Test Types and Recommended Tools
Unit Tests (/tests/unit/)
Validate isolated functions/modules.
- JavaScript/TypeScript: Jest + Testing Library
- Python: pytest + pytest-cov
- Rust: built-in
cargo test
Integration Tests (/tests/integration/)
Validate component interactions and data flow.
- API testing: Supertest (Node.js), requests (Python), reqwest (Rust)
- Data stores/dependencies: Testcontainers or equivalent isolated services
End-to-End Tests (/tests/e2e/)
Validate complete user journeys and system behavior.
- Web: Playwright or Cypress
- Mobile: Detox or Appium
Security Tests (/tests/security/)
Identify vulnerabilities and unsafe defaults.
- Static checks: ESLint plugin security, bandit, cargo-audit
- Dependency checks: npm audit, safety/pip-audit, cargo-audit
Performance Tests (/tests/performance/)
Validate latency, throughput, and memory behavior.
- Load tools: Artillery, k6, JMeter
- Profiling: Clinic.js, memory_profiler, language-native profilers
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.
- yesterday First seen · 183 lines · 0 tokens per session scan A ffebaec9035d
testing_guidelines_template is an agent published in the GitHub repository atebites-hub/PJTemplate (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,542 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.