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.
npx agentmods add skills/pekral/cursor-rules/record-project-memorynpx skills add pekral/cursor-rules --skill record-project-memorygit clone --depth 1 https://github.com/pekral/cursor-rulesWhat 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 | $0.00086 | $0.01561 |
| Opus 5 | $0.00043 | $0.00781 |
| Sonnet 5 | $0.00017 | $0.00312 |
| Haiku 4.5 | $0.00009 | $0.00156 |
Grade A, and why
record-project-memory 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constraints
- Apply
@rules/compound-engineering/general.mdcCompound Memory (per project) — this skill is the write side of that rule; it owns the promotion bar, the curation pass, and the file convention defined there. - Apply
@rules/git/general.mdc - Write-only to the memory file. This skill modifies exactly one file:
docs/memory/PROJECT_MEMORY.mdin the project being worked on. It never edits production code, tests, configuration,CLAUDE.md, or.cursor/rules/project.mdc. - Never record secrets, credentials, tokens, or PII — apply the same prohibition the security rules apply to logs and tracker comments. When a lesson can only be stated with a secret, generalize it until the secret is gone or drop the entry.
- Per-project only. The memory file lives in the target project, never in this shared rules package. Never write a project lesson into
rules/**as a global rule. - Output must be in English (the memory file is a code artifact, like
CLAUDE.md).
Use when
- A
@skills/resolve-issueor@skills/process-code-reviewrun has converged (review loop at 0 Critical / 0 Moderate) and is about to publish its final report. - An orchestrating run reaches its final report after the convergence gate.
- The user explicitly asks to record a lesson into project memory.
Do not run this skill mid-task, before convergence, or for a task that produced no durable lesson.
Inputs
CONVERGED_CONTEXT— required. The converged task context: what was implemented/fixed, the review findings that recurred, the wrong turns taken, and the design decisions made. The orchestrator passes this from the shared brief; a skill passes its own run context.SOURCE_REF— required. The PR / issue link to record in each entry'sSource:field.AGENT_ROLE— optional. The role writing this entry:orchestration,analysis,implementation,review, orshared. When omitted, defaults toshared. Written as theRole:field of every entry produced in this invocation. Pass the caller's own role — do not guess.
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.
- 2d ago First seen · 84 lines · 86 tokens per session scan A 3791833513a4
record-project-memory is a skill published in the GitHub repository pekral/cursor-rules (6 stars, last pushed 8d ago), licensed MIT. It adds 86 tokens to every session and 1,561 once invoked, about $0.0004 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
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
ponytail-gain
Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.
parse-table
Parse table definition to extract module name, model name, table name, and field definitions. First step of CRUD generation.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.
octane-development
Use this skill when working with Laravel Octane, a long-running PHP worker server (Swoole, FrankenPHP, RoadRunner) where the application boots once and serves many requests instead of rebooting for each request like PHP-FPM. Trigger when installing Octane or starting its server; configuring or detecting the active…
module:assistant
Add an AI assistant chat panel to any Laravel project — with tool calling, streaming, and MCP support.