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.
git clone --depth 1 https://github.com/tecnomanu/pampaWrote 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/rules/tecnomanu/pampa/pampa-testing-examples)<a href="https://agentmods.dev/rules/tecnomanu/pampa/pampa-testing-examples"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/pampa-testing-examples/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/rules/tecnomanu/pampa/pampa-testing-examples"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/pampa-testing-examples.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.00000 | $0.01023 |
| Opus 5.5 | $0.00000 | $0.00409 |
| Sonnet 5.5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
pampa-testing-examples 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PAMPA Testing & Examples Guide
This guide explains how to test PAMPA functionality using the provided examples and testing tools.
Available Examples
Chat App Example
- Location: examples/chat-app/
- Purpose: Real-world JavaScript project for testing indexing and search
- Features: Multiple modules, utility functions, complex codebase structure
- Use Case: Test semantic search on actual code patterns
Test Implementations (Private)
- Location:
test/test-implementations/ - Purpose: Private testing area for implementation experiments
- Features: Gitignored content, safe for sensitive tests
- Use Case: Test PAMPA with real codebases without exposing them publicly
Testing Workflow
1. Basic Functionality Test
# Index the chat-app example
npx pampa index examples/chat-app/
# Test search functionality
npx pampa search "validation function" -p examples/chat-app/
# Check project stats
npx pampa info examples/chat-app/
2. Private Implementation Testing
# Copy your real codebase to test-implementations for testing
cp -r /path/to/your/project test/test-implementations/my-project/
# Index and test with real code
npx pampa index test/test-implementations/my-project/
npx pampa search "your specific query" -p test/test-implementations/my-project/
# Content is gitignored, safe for testing
3. MCP Integration Test
# Start MCP server
npx pampa mcp
# Test MCP tools via CLI or agent:
# - get_project_stats(path="examples/chat-app")
# - search_code("user validation", path="examples/chat-app")
# - get_code_chunk(sha_from_search_results)
4. Update Workflow Test
# Make changes to example files
# Then test update functionality
npx pampa update examples/chat-app/
# Verify changes are reflected in search
npx pampa search "new function name" -p examples/chat-app/
Test Validation Points
Indexing Tests
- ✅ Database created at
examples/chat-app/.pampa/pampa.db - ✅ Chunks directory populated with
.gzfiles - ✅ Codemap generated at
examples/chat-app/pampa.codemap.json - ✅ Functions properly extracted and chunked
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.
- 2mo ago First seen · 145 lines · 0 tokens per session scan A c5509c4a4453
pampa-testing-examples is a cursor rule published in the GitHub repository tecnomanu/pampa (31 stars, last pushed 1y ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 1,023 tokens. 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-30.
Other cursor rules, from other repositories
fuzzing
Fuzzing setup and guidelines for skia-rs.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.
development-guidelines
⚠️ ALWAYS start with FREE tests before ANY paid content generation.
test
Rules for test files.