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 mayank-io/mstack --skill make-repeatablegit clone --depth 1 https://github.com/mayank-io/mstackWrote 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/mayank-io/mstack/make-repeatable)<a href="https://agentmods.dev/skills/mayank-io/mstack/make-repeatable"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/make-repeatable/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/mayank-io/mstack/make-repeatable"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/make-repeatable.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.02081 |
| Opus 5.5 | $0.00021 | $0.00832 |
| Sonnet 5.5 | $0.00011 | $0.00416 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade B, and why
make-repeatable scanned grade B 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 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
1. Verify the file was created: `ls ~/.claude/skills/[skill-name]/` How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make This Repeatable
Analyze the current conversation to identify what work should be made repeatable, then recommend whether to implement it as a skill or a plugin, and build it upon user approval.
When This Skill Applies
- User says "make this repeatable"
- User wants to automate a workflow they just performed
- User asks to "turn this into a command"
- User says "I'll need to do this again"
- Discussions about creating reusable patterns
Phase 1: Analysis
Step 1: Identify the Repeatable Work
Review the conversation history to identify:
- What was accomplished - The end result or goal
- Key steps taken - The sequence of actions
- Tools used - Which Claude Code tools were involved
- Inputs required - What information was needed from the user (these become $ARGUMENTS)
- Outputs produced - Files created, commands run, results generated
Step 2: Classify the Complexity
| Complexity | Characteristics |
|---|---|
| Simple | Single task, no external tools, just instructions |
| Moderate | Multi-step workflow, uses standard tools (Read, Edit, Bash) |
| Complex | Requires external APIs, custom tools, or persistent state |
Step 3: Evaluate Skill vs Plugin
Recommend a SKILL when:
- The workflow is primarily instructional (guiding Claude's behavior)
- No new tools or capabilities are needed
- Standard Claude Code tools suffice (Bash, Read, Edit, Grep, etc.)
- The pattern is a sequence of prompts/instructions
- No external service integration required
- No persistent configuration or state needed
Recommend a PLUGIN when:
- New tool capabilities are needed (custom tools)
- External API/service integration required (MCP servers)
- Hooks are needed (PreToolUse, PostToolUse, Stop)
- Multiple related skills should be bundled together
- Specialized agents are required
- Custom configuration/settings need to be stored
- The functionality extends Claude Code itself
Step 4: Recommend Scope
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 · 274 lines · 53 tokens per session scan B b2483a1e2301
make-repeatable is a skill published in the GitHub repository mayank-io/mstack (6 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 2,081 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.