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/mrjptech/macro-pickle/pickle-pipelinegit clone --depth 1 https://github.com/MrJPTech/macro-pickleWrote 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/commands/mrjptech/macro-pickle/pickle-pipeline)<a href="https://agentmods.dev/commands/mrjptech/macro-pickle/pickle-pipeline"><img src="https://agentmods.dev/badge/commands/mrjptech/macro-pickle/pickle-pipeline.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.1 | $0.00022 | $0.01048 |
| Opus 5 | $0.00011 | $0.00524 |
| Sonnet 5 | $0.00004 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
pickle-pipeline 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 6d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pickle-pipeline
Run the macro-pickle reference → video media pipeline: a two-stage, local,
Supabase-free flow that turns a rough idea into reference frames (Nano Banana),
lets you curate the keepers, then re-prompts those into video (Veo 3.1). Everything
writes to pipeline-output/<scene-slug>/; there is no database.
Replaces the old Supabase content-enrichment pipeline (translate → generate-images → generate,
pickle.*tables,sync-approved-to-supabase), which was removed with the CMS scaffold on 2026-06-29 (commit2b1f250). The code now lives inscripts/pipeline/*.ts+scripts/lib/pipeline/*.tson the toolkit clients.
Stages
- scene:new —
pnpm scene:new <slug>→ scaffoldpipeline-output/<slug>/scene.json(the recipe card: prompts + settings + a log of every file made). - scene:refs —
pnpm scene:refs <slug>→ Stage 1: the prompt enhancer rewrites your idea, then Nano Banana generates MANY candidate reference frames intopipeline-output/<slug>/references/. - curate (human gate) —
pnpm scene:select <slug> <ids>→ YOU pick the keeper frame ids that advance to video. - scene:analyze —
pnpm scene:analyze <slug>→ the vision analyzer "looks at" the keepers and grounds what it sees into the video prompt. - scene:video —
pnpm scene:video <slug>→ Stage 2: the keepers become video (Veo 3.1) as ingredients / first-last frames, written topipeline-output/<slug>/video/.
The curation gate (why this isn't one button)
Stages 1–2 automate; stage 3 (select) needs you to eyeball the candidates and choose
ids. So this command runs new → refs, then STOPS for curation. Re-invoke with
--from analyze (after pnpm scene:select) to finish analyze → video.
Arguments
$ARGUMENTS:
<scene-slug>— required; the scene folder name.--from <stage>— resume atrefs|analyze|video(e.g. after curating).--dry-run— print the enhanced prompt + planned commands without spending.
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.
- 6d ago First seen · 68 lines · 22 tokens per session scan A 29671501c6ae
pickle-pipeline is a command published in the GitHub repository MrJPTech/macro-pickle (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,048 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-31.
Other commands, from other repositories
brand-generate
Generate an on-brand document from a saved Brand Profile.
list
List available Piper TTS TTS voices with optional filtering.
review-video
Make a " Reviews" video — a fast, faceless VO montage of REAL, verified competitor reviews that names the recurring complaints and positions YOUR business as the alternative, then hands off to your own customer testimonials.
transcribe
Transcribe the file at $ARGUMENTS into Markdown using the Frenchie MCP server.
varyshop-carousel
Create a Varyshop multi-slide carousel (LIGHT style, hook → CTA).
imperium:create-video
Create startup video content. Supports pitch videos, product demos, social clips, investor updates, and hiring videos. Bridges to Remotion for rendering.