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.
git clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/plan-artifact)<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/plan-artifact"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/plan-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/commands/thibautbaissac/rails_ai_agents/plan-artifact"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/plan-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.00053 | $0.02318 |
| Opus 5.5 | $0.00021 | $0.00927 |
| Sonnet 5.5 | $0.00011 | $0.00464 |
| Haiku 4.5 | $0.00005 | $0.00232 |
Grade A, and why
plan-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.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presenting Plans
Create one unique, self-contained HTML artifact that helps the plan's intended audience understand what is being planned, why it matters, how it will likely unfold, and what decisions or risks remain.
Input
Plan: $ARGUMENTS
If $ARGUMENTS is empty or does not identify a readable local file, ask for the file path and stop.
Output requirement
Create a single .html file inside the artifacts/ directory in the current working directory.
If artifacts/ does not exist, create it.
The file must be fully self-contained:
- Include all CSS in a
<style>tag. - Include all JavaScript in a
<script>tag. - Do not depend on external CDNs, fonts, images, packages, or network requests.
- Use semantic HTML and accessible markup.
- Work by opening the file directly in a browser.
Name the file using a short slug derived from the plan title, for example:
artifacts/plan-artifact-[slug].html
If no clear title exists, use:
artifacts/plan-artifact.html
Do not overwrite an existing unrelated artifact unless the user explicitly asks. If the target filename exists, choose a clear variant such as artifacts/plan-artifact-[slug]-v2.html.
Core Principles
- Treat the source plan as authoritative.
- Prefer a polished strategy artifact over a raw document dump.
- Adapt the page structure to the plan type instead of forcing every plan into a product-feature template.
- Make the path from current state to target state legible without drowning the page in implementation minutiae.
- Keep the artifact useful when opened directly from disk, without any build step or network.
- Make missing details visible instead of filling gaps with confident guesses.
- The artifact should feel intentionally designed, not templated.
- Avoid generic dashboard filler, decorative-only graphics, excessive cards, repeated section layouts, and one-note color palettes.
Plan Type Detection
First classify the plan as one or more of these types:
- Product feature / PRD
- Technical implementation
- Migration / rollout
- Operations / incident response
- Research / discovery
- Business / go-to-market
- Organizational / process
- Architecture / platform strategy
- Other
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 · 271 lines · 53 tokens per session scan A 1620c95f3243
plan-artifact is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (672 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 2,318 once invoked, about $0.0002 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-30.
plan-artifact compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plan-artifactThibautBaissac/rails_ai_agents | Command | 672 | 5mo ago | MIT | A | 53 | Claude Code |
| brand-generateferdinandobons/brand-docs | Command | 291 | 3mo ago | MIT | A | 0 | Claude Code |
| cti-report7onez/cti-expert | Command | 622 | 15d ago | none | A | 45 | Claude Code |
| render-figuresbraininahat/brains-in-a-hat | Command | 4 | 18d ago | MIT | A | 17 | Claude Code |
| ppt-image2-editable-rebuildwwe-dog/ppt-image2-editable-rebuild | Command | 204 | 5mo ago | Unlicense | A | 15 | Claude Code |
| publish-api-docsnavraj007in/architecture-cowork-plugin | Command | 3 | 4mo ago | Apache-2.0 | A | 17 | Claude Code |
| write-patentjiutuhky/my-super-capsule | Command | 11 | 8mo ago | MIT | A | 48 | Claude Code |