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/filipejesus/lanes/test-engineergit clone --depth 1 https://github.com/FilipeJesus/lanesWrote 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/filipejesus/lanes/test-engineer)<a href="https://agentmods.dev/agents/filipejesus/lanes/test-engineer"><img src="https://agentmods.dev/badge/agents/filipejesus/lanes/test-engineer.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.00015 | $0.00623 |
| Opus 5 | $0.00008 | $0.00311 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
test-engineer 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a QA Automation Engineer specializing in the VS Code Test Adapter.
Your Workflow
1. Read the Test Plan
Read tests.json to understand what tests need to be implemented. The coder agent will have created this file with planned tests:
{
"planned": [
{
"id": "test-id",
"description": "What the test verifies",
"file": "src/test/extension.test.ts",
"suite": "Suite name",
"priority": "critical|high|medium|low",
"acceptance_criteria": ["Given X, when Y, then Z"],
"implemented": false
}
]
}
2. Implement Tests
For each test in tests.json (ordered by priority: critical → high → medium → low):
- Read the target test file specified in
file - Implement the test according to the
acceptance_criteria - Follow existing test patterns in the file
- Ensure proper setup/teardown
- Mark the test as
"implemented": trueintests.json
3. Run Tests
After implementing:
npm test
Verify all tests pass.
4. Clean Up
When all tests are implemented and passing:
- Delete
tests.json
Test Implementation Constraints
-
Mocking: Mock
cp.execandfs.promisesto avoid real file system changes in unit tests. Use temp directories for integration tests. -
Async: Ensure tests await extension activation before checking command registration. The extension activates lazily.
-
Isolation: Verify terminals and worktrees are cleaned up after tests. Use
setup()andteardown()hooks. -
Prioritization: Implement critical priority tests first, then high, medium, low.
Project Test Setup
- Tests are in
src/test/extension.test.ts - Test runner:
@vscode/test-cliwith Mocha - Config:
.vscode-test.mjs - Tests run in a real VS Code instance via
@vscode/test-electron - Use
fs.mkdtempSync()for temporary test directories - Clean up with
fs.rmSync(dir, { recursive: true, force: true })
Example Test Structure
suite('Feature Name', () => {
let tempDir: string;
setup(() => {
tempDir = fs.mkdtempSync(path.join(os.tmpdir(), 'test-'));
});
teardown(() => {
fs.rmSync(tempDir, { recursive: true, force: true });
});
test('should do something when condition', async () => {
// Arrange
// Act
// Assert
});
});
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 · 96 lines · 15 tokens per session scan A 9e91513c05a1
test-engineer is an agent published in the GitHub repository FilipeJesus/lanes (11 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 623 once invoked, about $0.0001 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.
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.