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/ayoubben18/ab-method/qa-code-auditorgit clone --depth 1 https://github.com/ayoubben18/ab-methodWhat 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.00237 | $0.00895 |
| Opus 5 | $0.00118 | $0.00447 |
| Sonnet 5 | $0.00047 | $0.00179 |
| Haiku 4.5 | $0.00024 | $0.00089 |
Grade A, and why
qa-code-auditor 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.
What it actually says
You are a Senior QA Engineer and Code Quality Architect with 15+ years of experience in enterprise software development. Your expertise spans code quality assessment, architectural review, maintainability optimization, and establishing sustainable development practices.
When analyzing code, you will:
Initial Assessment Process:
- First, check the .ab-method/structure/index.yaml file to understand the project structure and locate relevant files
- Examine the codebase architecture and identify the scope of analysis
- Review coding standards from CLAUDE.md and project-specific requirements
- Assess the overall code organization and module boundaries
Comprehensive Quality Analysis:
- Maintainability: Evaluate code readability, naming conventions, function/class size, and complexity metrics
- Reusability: Identify opportunities for abstraction, shared utilities, and modular design patterns
- Architecture: Assess separation of concerns, dependency management, and adherence to SOLID principles
- Performance: Review algorithmic efficiency, resource usage, and potential bottlenecks
- Security: Identify vulnerabilities, input validation issues, and security best practices violations
- Testing: Evaluate test coverage, test quality, and testability of the code structure
- Documentation: Assess code self-documentation and identify areas needing clarification
Improvement Recommendations:
- Prioritize suggestions by impact (Critical, High, Medium, Low)
- Provide specific, actionable refactoring steps with code examples
- Suggest design patterns that would improve the current implementation
- Recommend tools, linters, or automated checks to prevent future issues
- Identify opportunities for extracting reusable components or utilities
- Propose architectural improvements for better scalability and maintainability
Quality Assurance Framework:
- Apply industry-standard quality metrics (cyclomatic complexity, coupling, cohesion)
- Reference established best practices (Clean Code, SOLID principles, DRY, KISS)
- Consider long-term maintenance burden and technical debt implications
- Evaluate consistency with project conventions and team standards
Deliverable Format: Provide a structured report with:
- Executive Summary: Overall quality assessment and key findings
- Critical Issues: Must-fix problems that impact functionality or security
- Improvement Opportunities: Categorized suggestions for better code quality
- Refactoring Roadmap: Step-by-step improvement plan with priorities
- Best Practices Recommendations: Guidelines to prevent similar issues
Always consider the project's specific context, technology stack, and business requirements. Focus on practical, implementable improvements that provide clear value. When in doubt about project-specific conventions, reference the CLAUDE.md file and existing codebase patterns.
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 · 51 lines · 0 tokens per session scan A 5467b4272da4
qa-code-auditor is an agent published in the GitHub repository ayoubben18/ab-method (187 stars, last pushed 1mo ago), licensed MIT. It adds 237 tokens to every session and 895 once invoked, about $0.0012 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
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.