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 skills add openplanr/planr-pipeline --skill planr-artifactgit clone --depth 1 https://github.com/openplanr/planr-pipelineWrote 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/openplanr/planr-pipeline/planr-artifact)<a href="https://agentmods.dev/skills/openplanr/planr-pipeline/planr-artifact"><img src="https://agentmods.dev/badge/skills/openplanr/planr-pipeline/planr-artifact/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openplanr/planr-pipeline/planr-artifact"><img src="https://agentmods.dev/badge/skills/openplanr/planr-pipeline/planr-artifact.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00370 |
| Opus 5.5 | $0.00011 | $0.00148 |
| Sonnet 5.5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
planr-artifact 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 2mo 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
Planr Artifact
Use only the public planr artifact command. Never invoke planr-pipeline
directly and never relaunch Codex from inside this skill.
- For local review, run
planr artifact <file>orplanr artifact open <file>. Use--no-open --jsonin headless sessions. Generic artifacts default to the headlessdocumentpresentation. Use--presentation canvasonly when the user requests spatial/zoomable review; use--presentation documentto force the reading surface. - Sharing is always explicit. Run
planr artifact share <file>only after the user asks to share. Explain that fragment links contain encoded plaintext; encrypted short links store ciphertext and keep the key in the URL fragment. - For returned feedback, run
planr artifact import <review-url>. Do not add--allow-stalewithout showing the stale-review preview and obtaining the user's explicit approval. - Export a completed local session with
planr artifact export <session-id> --format json|markdown. - If the pipeline package is unavailable, report the exact corrective command
printed by
planr; do not bypass the runtime lock or managed state.
Local review is loopback-only. Opening, approving, finishing, or importing an artifact never publishes it automatically.
Artifact review bundles complete local HTML/CSS/JavaScript and presents it inside an invisible opaque-origin sandbox. It is private review, not standalone website hosting; never describe a share link as deploying the artifact itself.
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.
- 2mo ago First seen · 33 lines · 27 tokens per session scan A af0afc993261
planr-artifact is a skill published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 370 once invoked, about $0.0001 per session on Opus 5.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.
planr-artifact compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planr-artifactopenplanr/planr-pipeline | Skill | 2 | 1mo ago | MIT | A | 27 | Claude Code |
| mstar-conventionsbtspoony/mstar-harness | Skill | 68 | 2d ago | MIT | A | 98 | Claude Code |
| mstar-routing-evalbtspoony/mstar-harness | Skill | 68 | 2d ago | MIT | A | 129 | Claude Code, Cursor |
| mstar-hostbtspoony/mstar-harness | Skill | 68 | 2d ago | MIT | A | 55 | Claude Code |
| mstar-iterationbtspoony/mstar-harness | Skill | 68 | 2d ago | MIT | A | 45 | Claude Code |
| mstar-compound-refreshbtspoony/mstar-harness | Skill | 68 | 2d ago | MIT | A | 72 | Claude Code |
| mstar-design-mdbtspoony/mstar-harness | Skill | 68 | 2d ago | MIT | A | 60 | Claude Code |