pampa-mcp-usage

pampa-mcp-usage is a cursor rule for Cursor from tecnomanu/agent-rules-kit. It costs 0 tokens per session (359 once invoked), scanned A, original, ISC.

A project memory system that indexes a codebase and lets an agent search it by meaning, not only exact words.

In plain words
What is it for?
It is for checking whether a project is indexed, searching for related code, reading complete code sections, and creating or updating the project index.
Why use it?
It helps the agent find existing code before creating new functions and keeps its stored understanding aligned with later changes.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/tecnomanu/agent-rules-kit/pampa-mcp-usage
Clone the repo
git clone --depth 1 https://github.com/tecnomanu/agent-rules-kit

Made for: Cursor.

Wrote 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.

agentmods badge for pampa-mcp-usage

README.md
[![agentmods](https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit/pampa-mcp-usage.svg)](https://agentmods.dev/rules/tecnomanu/agent-rules-kit/pampa-mcp-usage)
Your own site
<a href="https://agentmods.dev/rules/tecnomanu/agent-rules-kit/pampa-mcp-usage"><img src="https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit/pampa-mcp-usage.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 359 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00359
Opus 5 $0.00000 $0.00179
Sonnet 5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

Measured 5d ago against content hash 073f48c48cba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pampa-mcp-usage 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 5d 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.

.cursor/rules/pampa-mcp-usage.mdc · 51 lines

What it actually says

PAMPA MCP Usage Rules

You have access to PAMPA, a code memory system that indexes and allows semantic search in projects.

Basic Instructions

  1. ALWAYS at the start of a session:

    • Run pampa_get_project_stats to check if the project is indexed
    • If no database exists, run pampa_index_project
    • Run pampa_update_project to sync with recent changes
  2. BEFORE creating any function:

    • Use pampa_search_code with semantic queries like "user authentication", "validate email", "error handling"
    • Review existing code with pampa_get_code_chunk before writing new code
  3. AFTER modifying code:

    • Run pampa_update_project to update the knowledge base
    • This keeps the project memory synchronized

Available Tools

  • pampa_search_code(query, limit) - Search code semantically
  • pampa_get_code_chunk(sha) - Get complete code of a chunk
  • pampa_index_project(path) - Index project for the first time
  • pampa_update_project(path) - Update index after changes
  • pampa_get_project_stats(path) - Get project statistics

Strategy

Use PAMPA as your project memory. Search before creating, keep updated after changes, and leverage existing knowledge to avoid code duplication.

Query Examples

"user authentication middleware"
"database connection setup"
"error handling patterns"
"form validation logic"
"API endpoint configuration"

Always use descriptive, intent-based queries that describe what the code does, not just keywords.

Changes

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.

  1. 5d ago First seen · 51 lines · 0 tokens per session scan A 073f48c48cba

Subscribe to this mod's changes

pampa-mcp-usage is a cursor rule published in the GitHub repository tecnomanu/agent-rules-kit (35 stars, last pushed 11mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 359 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.