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/RenRMT/claude-code-vba-skillsWrote 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/renrmt/claude-code-vba-skills/testing-guide)<a href="https://agentmods.dev/agents/renrmt/claude-code-vba-skills/testing-guide"><img src="https://agentmods.dev/badge/agents/renrmt/claude-code-vba-skills/testing-guide/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/renrmt/claude-code-vba-skills/testing-guide"><img src="https://agentmods.dev/badge/agents/renrmt/claude-code-vba-skills/testing-guide.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.00043 | $0.00773 |
| Opus 5.5 | $0.00017 | $0.00309 |
| Sonnet 5.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 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 — 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.
- 1mo 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 6mo ago), licensed MIT. It adds 43 tokens to every session and 773 once invoked, about $0.0002 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.