meetings-cleanup

meetings-cleanup is a skill for Claude Code from flonat/flonat-research. It costs 61 tokens per session (893 once invoked), scanned A, original, MIT.

A workflow for finding, archiving, and removing old meeting recordings and related files. It focuses on managing storage used by audio recordings, transcripts, and voice memos.

In plain words
What is it for?
Use it to check meeting-storage usage, find large files, archive old meetings, or delete processed audio recordings.
Why use it?
It helps identify what is using disk space and organize or remove recordings that are no longer needed.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to check meeting-storage usage, find large files, archive old meetings, or delete processed audio recordings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flonat/flonat-research/meetings-cleanup
Install

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.

Any agent
npx skills add flonat/flonat-research --skill meetings-cleanup
Clone the repo
git clone --depth 1 https://github.com/flonat/flonat-research

Made for: Claude Code.

Wrote 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.

agentmods badge for meetings-cleanup

README.md
[![agentmods](https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-cleanup/github.svg)](https://agentmods.dev/skills/flonat/flonat-research/meetings-cleanup)
Your own site
<a href="https://agentmods.dev/skills/flonat/flonat-research/meetings-cleanup"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-cleanup/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.

agentmods 80×15 button for meetings-cleanup

Your own site · 80×15
<a href="https://agentmods.dev/skills/flonat/flonat-research/meetings-cleanup"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/meetings-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 893 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 73
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Tool Misuse · line 79
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Rogue Agent · line 50
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Excessive Agency · line 84
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.00893
Opus 5 $0.00030 $0.00447
Sonnet 5 $0.00012 $0.00179
Haiku 4.5 $0.00006 $0.00089

Measured 7d ago against content hash 3bca8beaaa35, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

meetings-cleanup 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 7d 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.

skills/meetings-cleanup/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

meetings-cleanup

Help the user manage disk space and organize old recordings.

Check current usage

# Total disk usage for meetings
du -sh ~/vault/meetings/

# Breakdown: audio vs transcripts
echo "Audio files:"; find ~/vault/meetings -name "*.wav" -exec du -ch {} + 2>/dev/null | tail -1
echo "Transcripts:"; find ~/vault/meetings -name "*.md" -exec du -ch {} + 2>/dev/null | tail -1

# Count by type
echo "Meetings: $(find ~/vault/meetings -maxdepth 1 -name '*.md' | wc -l | tr -d ' ')"
echo "Memos: $(find ~/vault/meetings/memos -maxdepth 1 -name '*.md' 2>/dev/null | wc -l | tr -d ' ')"

# Largest files
find ~/vault/meetings -type f -exec du -sh {} \; | sort -rh | head -10

Present this to the user before taking any action.

Common cleanup tasks

Delete WAV originals (biggest space saver)

After transcription, the original .wav files are no longer needed for search or recap. They only matter if you want to re-transcribe with a better model.

# List WAV files and their sizes
find ~/vault/meetings -name "*.wav" -exec du -sh {} \;

# Delete them (ask user for confirmation first!)
find ~/vault/meetings -name "*.wav" -delete

Archive old meetings

Move meetings older than N days to an archive folder:

mkdir -p ~/vault/meetings/archive

# Find meetings older than 90 days
find ~/vault/meetings -maxdepth 1 -name "*.md" -mtime +90

# Move them (confirm with user first)
find ~/vault/meetings -maxdepth 1 -name "*.md" -mtime +90 -exec mv {} ~/vault/meetings/archive/ \;

Archived meetings won't appear in minutes list or minutes search (which only scans ~/vault/meetings/), but they're still on disk if needed.

Clean up processed voice memos

The watcher moves originals to ~/vault/meetings/memos/processed/ after transcription:

du -sh ~/vault/meetings/memos/processed/ 2>/dev/null

Clean up stale state

# Remove stale PID file
rm -f ~/.minutes/recording.pid

# Clean old logs (keep last 7 days)
find ~/.minutes/logs -name "*.log" -mtime +7 -delete 2>/dev/null

# Remove last-result.json (transient)
rm -f ~/.minutes/last-result.json

Read the full file on GitHub · 89 lines

Changes

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.

  1. 7d ago First seen · 89 lines · 61 tokens per session scan A 3bca8beaaa35

Subscribe to this mod's changes

meetings-cleanup is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 16d ago), licensed MIT. It adds 61 tokens to every session and 893 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories