Borrowing it
Nothing to install: this file belongs to ndjordjevic/pinrag. 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/ndjordjevic/pinrag/main/.cursor/skills/run-pinrag-unit-tests/SKILL.mdgit clone --depth 1 https://github.com/ndjordjevic/pinragWrote 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/ndjordjevic/pinrag/run-pinrag-unit-tests)<a href="https://agentmods.dev/skills/ndjordjevic/pinrag/run-pinrag-unit-tests"><img src="https://agentmods.dev/badge/skills/ndjordjevic/pinrag/run-pinrag-unit-tests/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/ndjordjevic/pinrag/run-pinrag-unit-tests"><img src="https://agentmods.dev/badge/skills/ndjordjevic/pinrag/run-pinrag-unit-tests.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.00051 | $0.00471 |
| Opus 5 | $0.00026 | $0.00235 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
run-pinrag-unit-tests 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 11d 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
Run PinRAG tests
From the pinrag repo root (directory with pyproject.toml), run the eval … pytest line below (one chained command). It reads ~/.cursor/mcp.json → mcpServers.pinrag-dev.env (OpenAI, OpenRouter, Anthropic, etc.—not “OpenAPI”). Use another mcpServers key: set it on the same line (see export below).
Secrets: never paste mcp.json values into chat.
export PINRAG_MCP_JSON_KEY="${PINRAG_MCP_JSON_KEY:-pinrag-dev}"; eval "$(python3 -c "import json, pathlib, shlex, os; k=os.environ[\"PINRAG_MCP_JSON_KEY\"]; e=json.loads((pathlib.Path.home()/\".cursor/mcp.json\").read_text()).get(\"mcpServers\",{}).get(k,{}).get(\"env\")or{}; [print(\"export \"+n+\"=\"+shlex.quote(str(e[n]))) for n in sorted(e)]")" && export PINRAG_LLM_PROVIDER="${PINRAG_LLM_PROVIDER_TEST:-openai}" PINRAG_LLM_MODEL="${PINRAG_LLM_MODEL_TEST:-gpt-4o-mini}" && uv sync --all-extras && uv run pytest
The PINRAG_LLM_* exports avoid failures when mcp.json pins OpenRouter but integration tests (e.g. multi-query) still hit OpenAI chat with a non-OpenAI model id. Drop them if your MCP entry already uses PINRAG_LLM_PROVIDER=openai with a real OpenAI chat model.
Fast run (no integration / PyPI MCP):
uv sync --extra dev && uv run pytest -m "not integration and not pypi_mcp"
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.
- 11d ago First seen · 22 lines · 51 tokens per session scan A 8d0addeefacc
run-pinrag-unit-tests is a skill published in the GitHub repository ndjordjevic/pinrag (2 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 471 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
test-scenarios
Validate feature with real test scenarios before commit. Verifies environment (Docker, VPN, DB), seeds test data, runs unit + integration tests, and executes manual smoke tests against local or staging. Use after /code-review and before /commit. Use when the user says "test", "testar", "test scenarios", "smoke test"…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.