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 timjensgrossinger/threnody --skill threnody-taskgit clone --depth 1 https://github.com/timjensgrossinger/threnodyWrote 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/timjensgrossinger/threnody/threnody-task)<a href="https://agentmods.dev/skills/timjensgrossinger/threnody/threnody-task"><img src="https://agentmods.dev/badge/skills/timjensgrossinger/threnody/threnody-task.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.00046 | $0.01056 |
| Opus 5 | $0.00023 | $0.00528 |
| Sonnet 5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
threnody-task 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threnody task orchestration
Execution phase after planning — see threnody-plan for plan-only vs
plan-then-execute routing.
Use this skill for planning + host wave execution without the full swarm
persistence contract (swarm_id, budget preview, resume checkpoints).
When to use
Use threnody-task |
Use threnody-swarm instead |
|---|---|
plan_task / decompose_task / fleet_plan |
execute_swarm |
Host runs host_spawn_waves |
Need swarm_id, telemetry, resume |
| No budget preview token flow | Budget preview + preview_token confirm |
| Single planning pass | Coordinator star rounds (delegate mode) |
Workflow
- Prefer
threnody-planfirst unless the user already approved a wave plan. route_task(task)— tier,execution_hint, optional singlehost_spawn.- Decompose (multi-concern work):
- Prefer
decompose_task(task)(alias ofplan_task). - Or
plan_task(task)directly.
- Prefer
- Read
host_spawn_wavesfrom the plan response. - Execute waves in order via host
Task/Agent:- Agents within one wave may run in parallel.
- Respect wave ordering (later waves wait for earlier dependencies).
- Reporting — check
learning_report_contract.report_mode:batch(default): do NOT callreport_host_waveper worker wave. Spawn waves; learning is captured automatically (PostToolUse hook) or passed in the single terminal call (learning_capture=model).inline(legacy):report_host_wave(host_run_id|plan_run_id, wave, workspace_root, agents[])after each wave withtask_id,spawn_id,success,touched_files,output_excerpt.
- Mid-run:
expand_host_plan(discovered_files=[...])when wave 1 discovers files not in the initial plan. - Final:
report_host_swarm_complete(outcome=...)once (batch imports + finalizes). Checkfinalize.swarm_outcome. - Optional:
fleet_plan(task)when you want ready-made fleet command strings per wave.
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.
- 7d ago First seen · 85 lines · 46 tokens per session scan A d709f3975cb2
threnody-task is a skill published in the GitHub repository timjensgrossinger/threnody (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,056 once invoked, about $0.0002 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
personetta-set-active
Switches the active Personetta persona via set-active. The target tool is auto-detected from the host agent (Claude Code here), so no --format is needed. Use when the user asks to change recipe, switch persona, or set active role.
personetta-current
Reports the active Personetta recipe id using the installed CLI. The host agent (Claude Code here) is auto-detected. Use when the user asks for their current persona, active recipe, or which Personetta role is on.
personetta-list
Lists Personetta recipes (and optionally roles) using the installed Personetta CLI. Use when the user asks what recipes or personas exist before switching.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.