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 skills/jnzader/repoforge/test_adaptersnpx skills add JNZader/repoforge --skill test_adaptersgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/test_adapters)<a href="https://agentmods.dev/skills/jnzader/repoforge/test_adapters"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_adapters.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.00027 | $0.00363 |
| Opus 5 | $0.00014 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
test-adapters-strip-yaml-frontmatter 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 5d 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.
What it actually says
test-adapters-strip-yaml-frontmatter
This skill covers testing the _strip_yaml_frontmatter helper.
Trigger: test_adapters.
Quick Reference
| Task | Pattern |
|---|---|
| Get users | get_users() |
| Sample skills | sample_skills |
Critical Patterns (Summary)
- Get Users: Retrieve user data for testing.
- Sample Skills: Access predefined skills for validation.
Critical Patterns (Detailed)
Get Users
This pattern retrieves user data for testing purposes using the get_users function.
users = get_users()
Sample Skills
This pattern accesses predefined skills for validation in tests.
skills = sample_skills
When to Use
- When validating user data in tests.
- When checking the integrity of sample skills.
Commands
pytest tests/test_adapters.py
Anti-Patterns
Don't: Use hardcoded values
Hardcoded values can lead to brittle tests that fail with changes in data.
# BAD
assert user['name'] == 'John Doe'
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.
- 5d ago First seen · 78 lines · 27 tokens per session scan A 2c2f3f8ec11b
test-adapters-strip-yaml-frontmatter is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 363 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-31.
Other skills, from other repositories
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
write-sglang-test
Guide for writing SGLang CI/UT tests. Covers CustomTestCase, CI registration, server fixtures, model selection, mock testing, and test placement. Always read test/README.md for the full CI layout, how to run tests, and extra tips. Use when creating new tests, adding CI test cases, writing unit tests, or when the user…
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.