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_scorer/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_scorer)<a href="https://agentmods.dev/skills/jnzader/repoforge/test_scorer"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_scorer/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_scorer"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_scorer.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.00035 | $0.00454 |
| Opus 5 | $0.00017 | $0.00227 |
| Sonnet 5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
add-test-scorer-endpoint 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 9d 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
add-test-scorer-endpoint
This skill covers patterns for creating and managing test scorer endpoints.
Trigger: Load this skill when working with the test_scorer module.
Quick Reference
| Task | Pattern |
|---|---|
| Create a user | create_user |
| Retrieve users | get_users |
Critical Patterns (Summary)
- Create User: Use
create_userto add a new user to the system. - Get Users: Utilize
get_usersto fetch a list of all users.
Critical Patterns (Detailed)
Create User
Use create_user to add a new user to the system, ensuring proper data handling.
from tests.test_scorer import create_user
new_user = create_user(name="John Doe", email="[email protected]")
Get Users
Utilize get_users to fetch a list of all users, which can be useful for displaying user data.
from tests.test_scorer import get_users
users = get_users()
When to Use
- When you need to add new users for testing purposes.
- When retrieving user data for validation in tests.
Commands
pytest tests/test_scorer.py
Anti-Patterns
Don't: Hardcode User Data
Hardcoding user data can lead to brittle tests that fail with changes in requirements.
# 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.
- 9d ago First seen · 82 lines · 35 tokens per session scan A 6d5ecd0b7c23
add-test-scorer-endpoint is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 454 once invoked, about $0.0002 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
ai-regression-testing
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
groq-inference
Ultra-fast LLM inference on custom LPU hardware. OpenAI-compatible API at api.groq.com. Lowest latency in the industry (500-1000+ tok/s). Supports chat completions, vision, audio (Whisper STT + TTS), tool calling, JSON mode, and streaming. Free tier available. Inference only — no training.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
bun-file-io
Use this when you are working on file operations like reading, writing, scanning, or deleting files. It summarizes the preferred file APIs and patterns used in this repo. It also notes when to use filesystem helpers for directories.
protocolsio-integration
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io…