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_plugins/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_plugins)<a href="https://agentmods.dev/skills/jnzader/repoforge/test_plugins"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_plugins/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_plugins"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_plugins.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.00028 | $0.00410 |
| Opus 5.5 | $0.00011 | $0.00164 |
| Sonnet 5.5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
test-plugins-build-commands 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-plugins-build-commands
This skill covers testing plugins for various repository types.
Trigger: Load this skill when working with test_plugins.
Quick Reference
| Task | Pattern |
|---|---|
| Map Python repositories | python_repo_map |
| Map Node repositories | node_repo_map |
Critical Patterns (Summary)
- Python Repository Mapping: Use
python_repo_mapto map Python repositories. - Node Repository Mapping: Use
node_repo_mapto map Node.js repositories.
Critical Patterns (Detailed)
Python Repository Mapping
Utilize python_repo_map to effectively map Python repositories for testing.
# Example of using python_repo_map
repo_mapping = python_repo_map()
Node Repository Mapping
Leverage node_repo_map to map Node.js repositories for your testing needs.
# Example of using node_repo_map
node_mapping = node_repo_map()
When to Use
- When you need to test Python plugins in a repository.
- When you are validating Node.js plugins in your project.
Commands
pytest tests/test_plugins.py
Anti-Patterns
Don't: Hardcode Repository Paths
Hardcoding paths can lead to maintenance issues and reduce flexibility.
# BAD
repo_path = "/path/to/repo"
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 · 80 lines · 28 tokens per session scan A f5d0fed85927
test-plugins-build-commands is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 24d ago), licensed MIT. It adds 28 tokens to every session and 410 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
reproduce
Reproduces a paper's result, a claim, an artifact or a previous run with the target and success criterion frozen first, the canonical code path run before any substitute, exact inputs, environment, seeds and commands captured, and a verdict from a fixed set, reproduced, reproduced within tolerance, partially…
acceptance-checks
Turns the acceptance criteria a task states into executable checks and runs them against the finished outputs before delivering, rather than trusting that a correct-looking analysis satisfies them; rehearses the hidden condition when the grader scores unseen instances from a described family; treats a stated formula…
submitted-code
Writes code that survives being re-executed by someone else on inputs you never saw, targeting the grader's or collaborator's runtime rather than your own, with one self-contained entry point using only the libraries the specification names, no reliance on packages you installed or files you cached during development…
tmux-manual-qa
Run a single manual tmux-based QA scenario for the todo continuation feature against the real CLI (./pi-test.sh) in an interactive TUI. Captures scrollback, asserts deterministic pass/fail count markers, and cleans up test fixtures. Use only for the manual-qa milestone features.
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
rpa-init
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.