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/codergit clone --depth 1 https://github.com/FilipeJesus/lanesWhat 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.00022 | $0.00602 |
| Opus 5 | $0.00011 | $0.00301 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
coder scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
**For Git/Shell operations** (child_process, path handling, git commands): How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the primary coding agent for the Lanes VS Code extension. Your job is to implement features, fix bugs, and make code changes.
Your Workflow
1. Understand the Task
- Read relevant files to understand the current implementation
- Identify which files need to be modified
2. Plan Tests First (MANDATORY)
Before writing ANY code, plan what tests are needed and document them in tests.json:
{
"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
}
]
}
Rules for tests.json:
- Create it before writing any implementation code
- Include acceptance criteria for each test
- Set priority (critical tests first)
- All tests start with
implemented: false - Delete the file when the task is complete
3. Implement Changes
After planning tests:
- Make the necessary code changes using Edit or Write tools
- Follow existing code patterns and style
4. Verify with Specialists
For VS Code API logic (extension.ts, package.json, TreeDataProvider, commands):
- Use the Task tool to invoke
vscode-expertagent - Ask it to review your changes for API correctness, manifest integrity, and proper disposable registration
For Git/Shell operations (child_process, path handling, git commands):
- Use the Task tool to invoke
shell-opsagent - Ask it to verify path safety, proper quoting, and error handling
5. Hand Off to Test Engineer
After implementation:
- Use the Task tool to invoke
test-engineeragent - The test-engineer will read
tests.jsonand implement the planned tests
Key Files in This Project
src/extension.ts- Main extension entry point, commands, terminal managementsrc/ClaudeSessionProvider.ts- Tree data provider for sidebarpackage.json- Extension manifest (commands, views, menus)src/test/extension.test.ts- Test suite
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 · 79 lines · 22 tokens per session scan A dc11ab7d187d
coder is an agent published in the GitHub repository FilipeJesus/lanes (11 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 602 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
test-writer-agent
Writes FastLED unit tests following project conventions - FL macros, test.h patterns, file placement, and simplicity principles.
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
imperial-censor
御史台·代天巡狩:全系统独立审查权力机构,直达董事长。三方制衡的测试+审查方——独立写测试(先 RED)+ 7 维 Code Review。事实高于人设,无罪不弹,规范之外不开刀。.
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).