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 stefanoskarakasis/Product-Marketing-Skills --skill industry-newslettergit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-SkillsWrote 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/stefanoskarakasis/product-marketing-skills/industry-newsletter)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/industry-newsletter"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/industry-newsletter/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/stefanoskarakasis/product-marketing-skills/industry-newsletter"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/industry-newsletter.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.00198 | $0.07391 |
| Opus 5.5 | $0.00079 | $0.02956 |
| Sonnet 5.5 | $0.00040 | $0.01478 |
| Haiku 4.5 | $0.00020 | $0.00739 |
Grade A, and why
industry-newsletter 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 2d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Industry Newsletter
A C-suite reader will not read a feed, and a colleague in another department will not read a long update. They read one forwardable page that tells them what changed with your competitors and in your industry, what it means for deals, and who owns the next step. This skill builds that page every week in a locked layout, so Product, Sales, RevOps and PMM always know where to look, and so the update keeps your leadership informed and your other departments close to CI. It asks once where the issue will be read (Google Doc, email or Slack) and formats for that place. What makes it worth reading week after week is the loop: each issue grades its last call, carries unresolved signals forward and, once readers have told it enough, proposes how to change itself. It researches public sources only, never writes the brain, and does not replace the roster brief with a euro decision (competitive-briefing).
Trigger
- When: A PMM or CI lead needs the recurring read on competitors and the industry for GTM leaders and other departments, as a Google Doc, an email or a Slack post.
- Not for: The euro-quantified decision brief for the CEO, CRO or board on your roster →
competitive-briefing. A weekly list of up to five opportunities tied to brain priorities →signal-monitor. One question about one competitor →competitive-profile. The one-page card for a live deal →competitive-battlecard. A long sourced document for one decision →competitor-deep-dive. A public-facing newsletter or blog →writing-assistant. Mapping who buyers compare you to →alternatives-map. - Example prompts:
- "Write this week's industry newsletter for fintech in EMEA."
- "Weekly competitor and industry newsletter for our exec team."
- "Industry newsletter for the exec team, formatted for Slack in #ci-fintech."
- "Grade the last industry newsletter call and show what we are still watching." (edge: grades the ledger and lists the watchlist; a full issue only if asked)
- "Send the newsletter." (edge: no roster, no category and nothing retrieved, so the evidence floor stops the build)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 278 lines · 198 tokens per session scan A 093100bb4717
industry-newsletter is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed 3d ago), licensed MIT. It adds 198 tokens to every session and 7,391 once invoked, about $0.0008 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-10-28.
Other skills, from other repositories
report
A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.
k8s-rightsize
Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".
owasp-security
Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.
fig
One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
workspace-rules
A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.