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/icloudza/algokiller-plugin/foldgit clone --depth 1 https://github.com/icloudza/algokiller-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.00037 | $0.00323 |
| Opus 5 | $0.00018 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
fold 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.
What it actually says
Use this when the bound trace is so large that subsequent trace_constscan / trace_search calls feel slow, especially when the trace contains long repeating instruction blocks (hash main loops, AES rounds in a loop, VM dispatch loops).
Steps:
- Sanity-check the binding. If no trace is bound, stop and tell the user.
- Run
trace_foldwith sensible defaults for the bound trace's shape. For hash-loop-heavy traces useblock=4, threshold=100; for VM-dispatch heavy useblock=2; for unknown useblock=4, threshold=200. Direct the output toout_filename(relative, lands inside the current artifacts_dir). - Report the size delta to the user: "trace_fold collapsed X MB → Y MB (Z %)". Pull the byte counts from the
trace_foldresponse. - Ask the user if they want to
bind_traceto the folded version. If yes, callbind_trace(path=<folded path>, mode=<same mode>). The folded trace's line numbers do NOT correspond to the original, so any line-number anchors from prior analysis become invalid — warn the user before rebinding.
DO NOT silently rebind. The folded trace is a derivative artifact, and using it requires user acknowledgement that line numbers don't carry over.
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 · 15 lines · 37 tokens per session scan A d98754f9b1f1
fold is a command published in the GitHub repository icloudza/algokiller-plugin (77 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 323 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-08-30.
Other commands, from other repositories
workflow-foundation-to-design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff.
workflow-product-strategy
Run the Product Strategy workflow (competitive analysis -> stakeholders -> opportunities -> solution -> ADR).
scan-suspicious-files
Scan file system for suspicious files in common malware locations.
memcord-save-progress
Auto-summarize and save conversation progress.
memcord-unbind
Remove .memcord binding from a project directory.
enrich
Enrich project memory by mining 100 recently merged PRs: extracts decisions, conventions, gotchas, and architectural facts from PR discussions, review comments, and PR bodies.