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 skills/smk-labs/claude-plugins/stepsnpx skills add smk-labs/claude-plugins --skill stepsgit clone --depth 1 https://github.com/smk-labs/claude-pluginsWrote 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/smk-labs/claude-plugins/steps)<a href="https://agentmods.dev/skills/smk-labs/claude-plugins/steps"><img src="https://agentmods.dev/badge/skills/smk-labs/claude-plugins/steps.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 | $0.00110 | $0.00328 |
| Opus 5 | $0.00055 | $0.00164 |
| Sonnet 5 | $0.00022 | $0.00066 |
| Haiku 4.5 | $0.00011 | $0.00033 |
Grade C, and why
steps scanned grade C with 1 finding 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
دستورالعمل گامبهگام به زبان ساده برای انجام یک کار: گرفتن کلید API، راهاندازی یک سرویس یا ابزار، کار اداری، هر روال چندمرحلهای. فقط گامهایی که خود کاربر باید انجام دهد. Use when the user says "چطور", "چه جوری", "دست What it actually says
steps: دستورالعمل گامبهگام
- اگر مراحل به UI یا قوانین روز وابسته است (پنل سرویسها، کارهای اداری)، اول وب را چک کن که مراحل امروز درست باشد. از حافظهٔ کهنه دستورالعمل نده.
- خروجی: کارت فارسی. فقط گامهای خود کاربر، شمارهدار. هر گام یک جملهٔ سادهٔ 15 تا 20 کلمهای. پیشنیازها اول. لینک و مسیر داخل code. هیچ گامی که «برای من بدیهی و برای کاربر گنگ» است جا نماند.
- اگر ادامهٔ کار را خودم میتوانم انجام دهم (مثل ذخیرهٔ توکن در جای درست و تستش با یک کال واقعی)، در پایان پیشنهاد بده؛ بدون تأیید انجام نده.
- طول: کوتاهترین نسخهٔ کامل. اگر مسیر چند حالت دارد، اول حالت اصلی، بعد یک خط برای استثناها.
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.
- 4d ago First seen · 13 lines · 110 tokens per session scan C 5e657ad96f3b
steps is a skill published in the GitHub repository smk-labs/claude-plugins (11 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 328 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.