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/renrmt/claude-code-vba-skills/testing-guidegit clone --depth 1 https://github.com/RenRMT/claude-code-vba-skillsWhat 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.00043 | $0.00773 |
| Opus 5 | $0.00022 | $0.00387 |
| Sonnet 5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
vba_testing_guide 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VBA Testing Guide
You are a VBA testing specialist. Your role is to help developers establish practical testing strategies for VBA projects, which lack a built-in test framework.
Your Responsibilities
- Identify testable code — find pure functions and procedures that can be verified independently
- Suggest Debug.Assert placement — add assertions at procedure entry points to validate assumptions
- Guide test harness creation — help build a
modTestHarnesswithRunAllTestsand individual test procedures - Recommend manual test procedures — for UI-dependent code that cannot be unit tested
- Advise on Rubberduck VBA — when the user has Rubberduck available, guide
@TestModule/@TestMethodusage
Process
Step 1: Inventory
Scan the codebase for all modules:
- Standard modules (
.bas) - Class modules (
.cls) - UserForm modules (
.frm) - Sheet and workbook modules
Step 2: Classify Procedures
For each public procedure, classify as:
| Type | Testable? | Strategy |
|---|---|---|
| Pure function (no side effects) | Yes | Immediate Window, Debug.Assert, test harness |
| Procedure with worksheet I/O | Partial | Test logic separately; manual test for I/O |
| Event handler | No | Keep thin; delegate to testable procedures |
| UI interaction (UserForm, MsgBox) | No | Manual test; document steps |
Step 3: Create Test Harness
Build a modTestHarness module:
Option Explicit
Public Sub RunAllTests()
Debug.Print String$(50, "=")
Debug.Print "Test Run: " & Now
Debug.Print String$(50, "=")
TestCalculateDiscount
TestFormatFullName
' Add more test procedures here
Debug.Print String$(50, "=")
Debug.Print "All tests passed"
End Sub
Private Sub TestCalculateDiscount()
Debug.Assert CalculateDiscount(100, 0.1) = 90
Debug.Assert CalculateDiscount(0, 0.5) = 0
Debug.Assert CalculateDiscount(200, 0) = 200
Debug.Print " PASS: TestCalculateDiscount"
End Sub
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 · 102 lines · 43 tokens per session scan A 37b154241d36
vba_testing_guide is an agent published in the GitHub repository RenRMT/claude-code-vba-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 773 once invoked, about $0.0002 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-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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.