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/laurigates/claude-plugins/configure-memory-profilingnpx skills add laurigates/claude-plugins --skill configure-memory-profilinggit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/configure-memory-profiling)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-memory-profiling"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-memory-profiling.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02010 |
| Opus 5 | $0.00017 | $0.01005 |
| Sonnet 5 | $0.00007 | $0.00402 |
| Haiku 4.5 | $0.00003 | $0.00201 |
Grade A, and why
configure-memory-profiling 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 yesterday.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:memory-profiling
Check and configure memory profiling infrastructure for Python projects using pytest-memray.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up memory profiling for a Python project from scratch | Project is not Python — memray/pytest-memray are Python-only |
| Adding pytest-memray integration for CI memory regression detection | Profiling CPU performance — use cProfile or py-spy instead |
| Configuring memory leak detection in test suites | Running load/stress tests — use /configure:load-tests |
| Setting memory thresholds and allocation benchmarks for CI | Quick one-off memory check — run uv run pytest --memray directly |
| Enabling native C extension stack tracking for deep profiling | Profiling production systems live — use memray standalone or Grafana |
Context
- Project root: !
pwd - Python project: !
find . -maxdepth 1 \( -name 'pyproject.toml' -o -name 'setup.py' \) - pytest-memray installed: !
find . -maxdepth 1 \( -name 'pyproject.toml' -o -name 'requirements*.txt' \) -exec grep 'pytest-memray' {} + - memray installed: !
find . -maxdepth 1 \( -name 'pyproject.toml' -o -name 'requirements*.txt' \) -exec grep 'memray' {} + - Conftest fixtures: !
find . -path '*/tests/*' -maxdepth 2 -name 'conftest.py' -exec grep -l 'memray' {} + - Memory test files: !
find . -path '*/tests/*' -maxdepth 3 -name '*memory*' -o -name '*memray*' - Benchmark tests: !
find . -path '*/tests/*' -maxdepth 3 -type d -name 'benchmarks' - CI workflows: !
find . -path '*/.github/workflows/*' -maxdepth 3 -name '*memory*' - Memory reports dir: !
find . -maxdepth 1 -type d -name 'memory-reports'
Parameters
Parse from $ARGUMENTS:
--check-only: Report memory profiling compliance status without modifications--fix: Apply all fixes automatically without prompting--threshold <mb>: Set default memory threshold in MB (default: 100)--native: Enable native stack tracking for C extensions
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.
- yesterday First seen · 199 lines · 34 tokens per session scan A 43896dfc4d98
configure-memory-profiling is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 2,010 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-adversarial-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-integration-to-unit-migrating
Use this skill ONLY when the user explicitly requests an audit, migration, or evaluation of whether a Shopware integration test belongs in the unit suite — trigger phrases like "audit integration tests", "migrate integration tests to unit", "is this an integration test or a unit test", "evaluate integration tests for…
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…