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 commands/synaptic-labs-ai/pact-plugin/prune-memorygit clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-PluginWhat 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.00017 | $0.06706 |
| Opus 5 | $0.00009 | $0.03353 |
| Sonnet 5 | $0.00003 | $0.01341 |
| Haiku 4.5 | $0.00002 | $0.00671 |
Grade A, and why
prune-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 3d 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 — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this command does
Presents the curator with the current evictable-pin list, asks which
one (or none) to remove, archives the selected pin to long-term memory
and verifies the archive before removing anything, then removes it.
Useful after /PACT:pin-memory is denied by the count cap: use
/PACT:prune-memory to demote an existing pin to long-term memory, then
retry the add.
Demotion is not deletion. A pin leaves ## Pinned Context only once its
content is provably somewhere else — see Step 3.
The pin_caps_gate PreToolUse hook ALLOWS the resulting Edit because
the pin count strictly decreases (net-worse predicate: pre has ≥N
pins, post has N-1 — not worse, so allow). The hook cannot enforce the
archive: it sees a count decrease and allows it, whether or not Step 3
ran. Step 3 is enforced by this file and by nothing else, which is why
every exit below emits a journal event — an invocation that evicts a pin
while emitting nothing is the one state that should never occur.
Process
Step 1 — Read the evictable-pin list
Invoke the advisory CLI to get the current state:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_pin_caps.py" --status
The CLI emits a JSON payload with evictable_pins:
{
"allowed": true,
"violation": null,
"slot_status": "Pin slots: N/12 used, ...",
"evictable_pins": [
{"index": 0, "heading": "First Pin", "chars": 40, "stale": false, "override": false,
"age_days": 60, "overdue": true},
{"index": 1, "heading": "Second Pin", "chars": 30, "stale": true, "override": false,
"age_days": null, "overdue": null},
...
]
}
age_days is computed from the pin's <!-- pinned: ... --> date comment;
overdue is true once that age reaches the staleness threshold. Both are
distinct from stale, which reports only that a <!-- STALE: ... --> marker
has been written into the body. A pin can be overdue without being stale.
age_days: null is a third state and is NOT overdue: false. It means the
pin carries no parseable date and its age is unknown. Surface it to the curator
as unknown rather than silently treating it as fresh — an undated pin is the one
most likely to have been sitting there longest.
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.
- 3d ago First seen · 507 lines · 17 tokens per session scan A c3a9dd3c3cfe
prune-memory is a command published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 6,706 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.