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/melodic-software/claude-code-plugins/generatenpx skills add melodic-software/claude-code-plugins --skill generategit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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.00072 | $0.01825 |
| Opus 5 | $0.00036 | $0.00912 |
| Sonnet 5 | $0.00014 | $0.00365 |
| Haiku 4.5 | $0.00007 | $0.00183 |
Grade A, and why
generate 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Variables
Arguments: $ARGUMENTS
Configured active profile: ${user_config.active_profile}
Purpose
Collect, deduplicate, rank, and present current AI-industry developments without depending on organization-specific configuration. Markdown is the default output. HTML and PPTX are explicit, optional outputs backed by the bundled deterministic build pipeline.
Source and access policy
Use only interfaces that authorize automated access:
- Official vendor blogs, documentation, changelogs, and release notes.
- GitHub release pages and repository APIs.
- RSS/Atom feeds listed by the selected profile.
- Reputable secondary reporting, corroborated by a primary source when practical.
- User-supplied public URLs and context.
Automated X/Twitter collection is disabled. Do not crawl, scrape, scroll, navigate, fetch, or extract X pages through browser automation, DOM scripts, unofficial endpoints, or Grok. Do not refresh following graphs or profile metadata. X's current terms expressly prohibit crawling or scraping without prior written consent: https://x.com/en/tos.
If the user supplies an X URL, preserve it as user-provided citation metadata but do not programmatically retrieve it. Ask for the relevant text when it is necessary, and seek a non-X primary source for corroboration. This plugin does not configure a paid X API.
Playwright is allowed only for deterministic rendering and inspection of locally generated HTML/PDF artifacts. It is not a collection provider.
Arguments
| Flag | Default | Effect |
|---|---|---|
--profile <name> |
Configured active_profile, then default |
Select a named profile for this invocation. |
--since <timeframe> |
14d | Accept 1d, 3d, 7d, 14d, 30d, or an ISO date. |
--providers <list> |
All | Limit collection to comma-separated provider buckets. |
--extras / --no-extras |
On | Include or omit robotics, science, and novel applications. |
--format <type> |
markdown |
Emit markdown, HTML, or PPTX. Non-markdown formats require prior /ai-briefing:setup apply install-build-deps. |
--yes / -y |
Off | Skip the pre-execution confirmation gate. Required for headless runs. |
What ships with it
51 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.
- evals/evals.json 7.4 KB
- evals/fixtures/archive-sample.md 2.1 KB
- evals/fixtures/candidate-items-sample.md 2.4 KB
- evals/fixtures/open-window-sample.md 1.3 KB
- output/build/assemble-html.js 2.9 KB runs code
- output/build/assets/logo-anthropic.svg 281 B
- output/build/assets/logo-bun.svg 1.7 KB
- output/build/assets/logo-cursor.svg 454 B
- output/build/assets/logo-google.svg 457 B
- output/build/assets/logo-huggingface.svg 3.0 KB
- output/build/assets/logo-langchain.svg 535 B
- output/build/assets/logo-meta.svg 1.3 KB
- output/build/assets/logo-microsoft.svg 206 B
- output/build/assets/logo-nvidia.svg 881 B
- output/build/assets/logo-openai.svg 1.5 KB
- output/build/assets/logo-tesla.svg 541 B
- output/build/assets/logo-visualstudiocode.svg 483 B
- output/build/assets/logo-x.svg 299 B
- output/build/brand.js 1.3 KB runs code
- output/build/build-client-js.js 5.4 KB runs code
- output/build/build-css.js 26 KB runs code
- output/build/build-html.js 184 B runs code
- output/build/build-pdf.js 1.6 KB runs code
- output/build/build-pptx.js 19 KB runs code
- output/build/build-sections.js 10 KB runs code
- output/build/emit-slides-data.js 6.7 KB runs code
- output/build/lib/brand-overlay.js 3.0 KB runs code
- output/build/lib/emit-slides.js 18 KB runs code
- output/build/lib/parse-briefing.js 14 KB runs code
- output/build/lib/paths.js 3.1 KB runs code
- output/build/lib/provider-logos.js 1.2 KB runs code
- output/build/lib/schema.js 4.7 KB runs code
- output/build/lib/url-display.js 1.1 KB runs code
- output/build/lib/url-policy.js 9.7 KB runs code
- output/build/lib/window.js 1.8 KB runs code
- output/build/package-lock.json 71 KB
- output/build/package.json 746 B
- output/build/run.js 2.5 KB runs code
- output/build/test/brand-overlay.test.js 4.5 KB runs code
- output/build/test/build-sinks.test.js 4.1 KB runs code
- output/build/test/parse-briefing.test.js 2.1 KB runs code
- output/build/test/paths.test.js 2.4 KB runs code
- output/build/test/provider-logos.test.js 669 B runs code
- output/build/test/schema.test.js 1.6 KB runs code
- output/build/test/url-policy.test.js 9.7 KB runs code
- output/build/test/window.test.js 1.9 KB runs code
- output/build/validate.js 17 KB runs code
- references/audience-defaults.md 3.5 KB
- references/build-pipeline.md 19 KB
- references/slide-generation.md 13 KB
- scripts/run-tests.sh 455 B runs 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.
- 2d ago First seen · 154 lines · 72 tokens per session scan A d8c190efda0e
generate is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 1,825 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.
adversarial-analysis
Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.
propagate-then-search
For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.