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 FlorianBruniaux/claude-code-plugins --skill guide-recapgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-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/florianbruniaux/claude-code-plugins/guide-recap)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/guide-recap"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/guide-recap/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/florianbruniaux/claude-code-plugins/guide-recap"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/guide-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01875 |
| Opus 5.5 | $0.00020 | $0.00750 |
| Sonnet 5.5 | $0.00010 | $0.00375 |
| Haiku 4.5 | $0.00005 | $0.00187 |
Grade A, and why
guide-recap 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 1mo 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide Recap
Generate social media content from CHANGELOG.md entries. Produces 8 outputs by default (4 formats x 2 languages).
When to Use
- After running
/releaseto create social announcements - Weekly to summarize multiple releases
- Before posting on LinkedIn, Twitter/X, newsletter, or Slack
Usage
/guide-recap latest # Latest released version
/guide-recap v3.20.5 # Specific version
/guide-recap week # Current week (Monday to today)
/guide-recap week 2026-01-27 # Specific week (Monday to Sunday)
Flags
| Flag | Effect | Default |
|---|---|---|
--interactive |
Guide mode: choose angle, audience, highlight | Off (auto-draft) |
--format=X |
Single format: linkedin, twitter, newsletter, slack |
All 4 formats |
--lang=X |
Single language: fr, en |
Both FR + EN |
--save |
Save output to [project-docs]/social-posts/ |
Display only |
--force |
Generate even if only maintenance entries | Skip low-score |
Workflow (7 Steps)
Step 1: Parse Input
Parse $ARGUMENTS to determine mode:
| Input | Mode | Target |
|---|---|---|
latest |
Single version | First ## [X.Y.Z] after [Unreleased] |
vX.Y.Z or X.Y.Z |
Single version | Exact version match |
week |
Week range | Monday of current week -> today |
week YYYY-MM-DD |
Week range | That Monday -> following Sunday |
If no argument or invalid argument, display usage and exit.
Step 2: Extract CHANGELOG Entries
Read CHANGELOG.md from the project root.
Single version:
- Find line matching
## [{version}] - Extract all content until next
## [line - Parse
### Added,### Changed,### Fixedsections
Week range:
- Collect all
## [X.Y.Z] - YYYY-MM-DDentries where date falls in range - Parse all sections from all matching versions
Error: version not found -> List last 5 versions, suggest latest.
Error: week has no entries -> Show date of last release, suggest that version.
What ships with it
9 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.
- assets/linkedin-template.md 2.4 KB
- assets/newsletter-template.md 2.9 KB
- assets/slack-template.md 2.0 KB
- assets/twitter-template.md 2.1 KB
- examples/version-output.md 5.3 KB
- examples/week-output.md 7.8 KB
- references/changelog-parsing-rules.md 4.8 KB
- references/content-transformation.md 4.3 KB
- references/tone-guidelines.md 2.9 KB
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.
- 1mo ago First seen · 220 lines · 50 tokens per session scan A d14928b51d55
guide-recap is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,875 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
submit-hook
Submit a deployed Uniswap v4 hook to the public univ4-hooks registry - format the listing, open a PR (issue fallback) so it lists on the hook marketplace.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
changelog
Use when a release is being prepared and the site changelog page needs the new version, after task release:prepare regenerated CHANGELOG.md, or when the user asks to update the changelog page, write release notes for the site, or backfill a version on docs/src/content/docs/changelog.md. User-facing write-up per…
release
Versioning and CHANGELOG: SemVer mapped from Conventional Commits, Keep a Changelog format, tagging, pre-release gates. Use when cutting a version: bumping, writing the CHANGELOG entry, or tagging.