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/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/plugins/smk-labs/claude-plugins/daily-tools)<a href="https://agentmods.dev/plugins/smk-labs/claude-plugins/daily-tools"><img src="https://agentmods.dev/badge/plugins/smk-labs/claude-plugins/daily-tools/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/plugins/smk-labs/claude-plugins/daily-tools"><img src="https://agentmods.dev/badge/plugins/smk-labs/claude-plugins/daily-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade C, and why
daily-tools 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 29d 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.
{"name": "daily-tools", "description": "اسکیلهای روزمره: swarm-qa (کیوای سوارمی چهار فازی), mkprompt-goal (پرامپت هدفمحور و ادامهپذیر), mkprompt-classic (پرامپت تشریحی با نقش و گاردریل), mkprompt-redesign (پرامپت بازط What it actually says
{"name": "daily-tools", "description": "اسکیلهای روزمره: swarm-qa (کیوای سوارمی چهار فازی), mkprompt-goal (پرامپت هدفمحور و ادامهپذیر), mkprompt-classic (پرامپت تشریحی با نقش و گاردریل), mkprompt-redesign (پرامپت بازطراحی چندراندی که به رنگ و فاصله تنزل نمیکند), mini-research (تحقیق سبک چندایجنتی), steps (دستورالعمل گامبهگام به زبان ساده), go (وضعیت فوقخلاصه و ادامهٔ کار), publish (گزارش با readable، صفحه روی پورتال، ایمیل کوتاه به لحن خودم), gouya (فارسی ساده و آدموار، فقط برای زبان فارسی).", "version": "2.5.0", "author": {"name": "Seyed M. Keramati", "url": "https://github.com/SMKeramati"}}What it installs
The manifest is a name and a version. 9 skills travel with it, and installing the plugin installs all of them — 615 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 29d ago Changed d34ea9e36b80
- 1mo ago Changed fb9c1beda7ad
- 1mo ago First seen · 1 lines scan C 0b6c8884f95f
daily-tools is a plugin published in the GitHub repository smk-labs/claude-plugins (11 stars, last pushed 28d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
pmm-skills
Product marketing skills for B2B SaaS PMMs and GTM operators: positioning and messaging, ICP and buyer personas, competitive intelligence and battlecards, GTM strategy and launch tiering, OKRs, PRDs, retros, customer stories and a shared company brain for Claude Code and Claude.
pmm-positioning
Positioning and messaging skills for B2B SaaS PMMs: ICP, alternatives map, buyer personas, market context, brand voice, positioning statements, message house, proof points and messaging playbooks.
pmm-execution
Day-to-day PMM execution skills: PRDs, OKRs, pre-mortems, retros, stakeholder maps, interview summaries, experiment docs and prioritization frameworks.
pmm-go-to-market
Go-to-market skills for PMMs: beachhead segments, launch tiering and GTM strategy briefs, GTM motions and multi-skill workflow orchestration.
pmm-growth
Growth skills for PMMs: North Star Metric and scorecard, positioning angles, campaign ideas, value-prop variants and checked customer stories.
pmm-intelligence
A weekly read on what changed around your product: at most five opportunities from signals you name, each tied to your brain and quarterly priorities.