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 skills add harshanandak/forge --skill test-lanegit clone --depth 1 https://github.com/harshanandak/forgeWrote 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/skills/harshanandak/forge/test-lane)<a href="https://agentmods.dev/skills/harshanandak/forge/test-lane"><img src="https://agentmods.dev/badge/skills/harshanandak/forge/test-lane.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.1 | $0.00064 | $0.00711 |
| Opus 5 | $0.00032 | $0.00356 |
| Sonnet 5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
test-lane 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-lane
A slow push is almost never a hang. It is the full-suite lane, and the full-suite lane is what an unmapped path buys you. [Forge #8 ×3]
The two lists that decide the lane
A changed path stays on the fast targeted lane only if it satisfies both:
isKnownTargetablePath(file)—scripts/test.js[verified 2026-08-13, around line 181]- It resolves to at least one real test file through
getTestCandidatesForChangedFile(file)/DIRECT_TEST_CANDIDATES—lib/commands/test.js[verified 2026-08-13, around lines 30 and 202]
Satisfy one and not the other and you still get the full suite: an unrecognised
path sets hasUnmappedFiles, and a recognised path that maps to zero existing
tests sets hasZeroResolvedTests. Either flag flips the plan to full.
Diagnose before you guess
node -e "console.log(JSON.stringify(require('./scripts/test.js').classifyPushTests(process.cwd()), null, 2))"
Read mode and reason. reason names the exact cause:
unmapped pushed files require full unit coverage,
known changes did not resolve runnable tests,
package-level changes detected,
or known changes mapped to targeted tests when you are on the fast lane.
Adding a new path
Both edits, in the same commit as the path itself:
scripts/test.js→ add the prefix toisKnownTargetablePath.lib/commands/test.js→ add the prefix togetTestCandidatesForChangedFile(or an exact entry inDIRECT_TEST_CANDIDATES), pointing at tests that exist.
Then re-run the classifier above and confirm mode: "targeted".
Rules
- Never widen a timeout to make a lane pass. A slow lane is a routing bug or a real regression. Bumping the budget hides both. [Forge #9 ×3]
- Never delete or vacuously weaken an assertion to get green. Same class. [Forge #9 ×3]
- Markdown that other suites read (README, AGENTS.md, docs/) also pulls in the
doc-asserting suites automatically — you do not need to list those by hand.
[verified 2026-08-13 —
selectDocAssertingTests,lib/commands/test.js] - Local green is not CI green. A targeted lane proves the mapped tests pass on
your machine, nothing more. Read
gh pr checksor the shepherd verdict before you call anything ready.
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.
- 7d ago First seen · 69 lines · 64 tokens per session scan A a2364bbdc022
test-lane is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 711 once invoked, about $0.0003 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 skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.