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/timjensgrossinger/threnody/threnody-fullstacknpx skills add timjensgrossinger/threnody --skill threnody-fullstackgit 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-fullstack)<a href="https://agentmods.dev/skills/timjensgrossinger/threnody/threnody-fullstack"><img src="https://agentmods.dev/badge/skills/timjensgrossinger/threnody/threnody-fullstack.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 | $0.00051 | $0.00926 |
| Opus 5 | $0.00026 | $0.00463 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
threnody-fullstack 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threnody full-stack parallel build
Threnody has no dedicated "app builder" mode. Use contract-first DAG planning so frontend and backend agents align before parallel execution.
Mandatory: spawn subagents
Full-stack orchestration uses the same contract as threnody-task and
threnody-swarm:
- Spawn one host
Task/Agentper subtask in each wave. - Never implement wave work yourself with Write/Edit — even for low-tier integration subtasks.
- Expect
host_execution_contract: spawn_subagentson plan/swarm responses.
Recommended wave shape
Wave 1: Define API contract
- OpenAPI spec, shared DTOs, route table
- produces: api-contract (openapi.yaml, shared types)
Wave 2: Parallel implementation (depends_on wave 1)
- Backend service/API handlers consumes: api-contract
- Frontend UI + client SDK consumes: api-contract
Wave 3: Integration
- Wire frontend to backend, smoke tests, fix drift
- depends_on: backend + frontend subtasks
Frontend and backend run in the same parallel wave only after the contract lands — not before.
Which MCP entry point?
| Goal | Tool | Topology |
|---|---|---|
| Plan once, host executes | decompose_task or plan_task |
Ask planner for DAG + depends_on |
| Persistence, budget, resume | execute_swarm |
topology: dag or auto |
Both return host_spawn_waves with spawn_subagents contract. Spawn one host
Task/Agent per subtask per wave — parallel wave 2 agents in one message.
Host-native heuristic planning also recognizes fullstack/openapi intent and
builds a contract-first DAG automatically. After wave 1, use expand_host_plan
if additional files were discovered.
Prompt the planner explicitly
Include in the task string:
- "Contract-first: wave 1 OpenAPI + shared types"
- "Wave 2: parallel frontend and backend consuming the contract"
- "Wave 3: integration and smoke tests"
- "Use depends_on / consumes / produces artifact names"
Example task for execute_swarm:
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 · 105 lines · 51 tokens per session scan A 49630432d744
threnody-fullstack is a skill published in the GitHub repository timjensgrossinger/threnody (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 51 tokens to every session and 926 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
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server…
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.
confluence-assistant
Central hub for Confluence operations - routes requests to specialized skills. ALWAYS use when user mentions confluence, wiki, or Atlassian wiki operations.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…