Borrowing it
Nothing to install: this file belongs to JNZader/repoforge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JNZader/repoforge/main/.claude/skills/main/test_compressor/SKILL.mdgit 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_compressor)<a href="https://agentmods.dev/skills/jnzader/repoforge/test_compressor"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_compressor/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/skills/jnzader/repoforge/test_compressor"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_compressor.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.00030 | $0.00447 |
| Opus 5.5 | $0.00012 | $0.00179 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
test-compressor-fixtures 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.
What it actually says
test-compressor-fixtures
This skill covers patterns for creating fixtures to test compression passes.
Trigger: Load this skill when working with test_compressor.
Quick Reference
| Task | Pattern |
|---|---|
| Create user fixture | create_user |
| Get user fixture | get_user |
Critical Patterns (Summary)
- Create User Fixture: Use
create_userto set up a user for testing. - Get User Fixture: Utilize
get_userto retrieve user data for tests.
Critical Patterns (Detailed)
Create User Fixture
Use create_user to set up a user for testing compression passes in your tests.
from tests.test_compressor import create_user
user = create_user(name="Test User", email="[email protected]")
Get User Fixture
Utilize get_user to retrieve user data for tests, ensuring the user exists before running tests.
from tests.test_compressor import get_user
user = get_user(user_id=1)
When to Use
- When you need to create a user for testing compression functionality.
- When you need to retrieve user data to validate compression results.
Commands
pytest tests/test_compressor.py
Anti-Patterns
Don't: Hardcode User Data
Hardcoding user data can lead to brittle tests that fail when data changes.
# BAD
user = create_user(name="Hardcoded User", email="[email protected]")
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 · 82 lines · 30 tokens per session scan A 5d933f829e17
test-compressor-fixtures is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 24d ago), licensed MIT. It adds 30 tokens to every session and 447 once invoked, about $0.0001 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 skills, from other repositories
knowledge-engineering-quality-and-delivery-unit-integration-and-shared-test-harnesses
A testing guide for the CLI and web interfaces, covering unit, integration, end-to-end, and real-process test setup with shared fixtures and cleanup.
test-writing
Write tests that catch real regressions — behavior-focused, minimal mocking, edge cases chosen from the code's actual branches. Use when adding tests for new code or backfilling tests for a fix.
csharp-testing
C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
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.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.