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/squared-lemons-ltd/podmule-plugin/workspace-triagenpx skills add Squared-Lemons-Ltd/podmule-plugin --skill workspace-triagegit clone --depth 1 https://github.com/Squared-Lemons-Ltd/podmule-pluginWrote 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/squared-lemons-ltd/podmule-plugin/workspace-triage)<a href="https://agentmods.dev/skills/squared-lemons-ltd/podmule-plugin/workspace-triage"><img src="https://agentmods.dev/badge/skills/squared-lemons-ltd/podmule-plugin/workspace-triage.svg" alt="Measured on agentmods" 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.00058 | $0.00554 |
| Opus 5 | $0.00029 | $0.00277 |
| Sonnet 5 | $0.00012 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
workspace-triage 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 5d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What needs attention today
A workspace with several shows accumulates work in places nobody looks: an episode recorded and never processed, clips drafted and never approved, an interview tomorrow with no notes. This skill is the sweep that surfaces them. It is entirely read-only — triage reports, it does not fix.
Establish where you are
list_workspaces shows which workspaces the account belongs to and which is currently active. Everything else operates on the active one, so a report that quietly covers the wrong workspace is worse than no report. switch_workspace moves between them when the user names one.
list_shows gives the shows in the workspace. Grouping by show is what makes the output usable — a flat list of twenty items across four podcasts is a list nobody acts on.
Where work goes stale
Episodes. search_episodes filters by show, status and published-date range. What is worth surfacing is the mismatch between state and time: a draft recorded weeks ago, an episode marked ready with no published date, a scheduled episode whose date has passed. match_episodes resolves a batch in one call when you already have the ids.
Clips. search_clips filters by episode and status. Drafts are unfinished work; authorised-but-unpublished are decisions already made that nobody executed. Those are two different kinds of outstanding and worth reporting separately.
Interviews. list_interviews is sorted by scheduled start. Read its status semantics carefully: confirmed does not become completed when the scheduled time passes, so a list of confirmed bookings mixes tomorrow's recording with one from last March. Filter on the date range yourself. Both directions matter — an interview in three days with no preparation, and a confirmed booking from six weeks ago that never became an episode.
What makes the report worth reading
Lead with what is urgent or already late, not with whatever the first query returned. Group by show. Say why each item is on the list — "recorded 3 weeks ago, still draft" tells someone what to do; "draft" does not.
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.
- 5d ago First seen · 31 lines · 58 tokens per session scan A e7bbf8884026
workspace-triage is a skill published in the GitHub repository Squared-Lemons-Ltd/podmule-plugin (0 stars, last pushed 18d ago), licensed MIT. It adds 58 tokens to every session and 554 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.