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 pjt222/agent-almanac --skill compose-sacred-musicgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/compose-sacred-music)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/compose-sacred-music"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/compose-sacred-music/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/pjt222/agent-almanac/compose-sacred-music"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/compose-sacred-music.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.00108 | $0.04058 |
| Opus 5.5 | $0.00043 | $0.01623 |
| Sonnet 5.5 | $0.00022 | $0.00812 |
| Haiku 4.5 | $0.00011 | $0.00406 |
Grade A, and why
compose-sacred-music 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose Sacred Music
Compose or analyze sacred music in Hildegard von Bingen's distinctive style, following her Symphonia harmoniae caelestium revelationum and modal composition principles.
When to Use
- You want to compose a new piece of sacred music in Hildegardian style
- You need to analyze an existing Hildegard chant for structure, mode, and text-setting
- You are researching medieval modal music and neumatic notation
- You want to understand the liturgical context of Hildegard's compositions
- You are preparing to perform or teach Hildegard's music
- You need guidance on text-setting for Latin sacred texts
Inputs
- Required: Purpose (compose new piece OR analyze existing piece)
- Required for composition: Sacred text (Latin preferred, English acceptable for study)
- Required for composition: Liturgical context (antiphon, sequence, responsory, hymn)
- Required for analysis: Title of Hildegard piece to analyze (e.g., "O vis aeternitatis")
- Optional: Feast day or liturgical season (influences modal choice)
- Optional: Intended performer experience level (simple syllabic vs. virtuosic melismatic)
- Optional: Mode preference (if composing)
Procedure
Step 1: Modal Selection (if composing) or Identification (if analyzing)
Choose or identify the liturgical mode that governs the melodic structure.
The Eight Church Modes (Medieval System):
┌──────┬─────────┬────────────┬──────────┬─────────────────────┐
│ Mode │ Name │ Final Note │ Range │ Character │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 1 │ Dorian │ D │ D-D │ Serious, meditative │
│ │ (auth.) │ │ (octave) │ Hildegard's most │
│ │ │ │ │ common │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 2 │ Dorian │ D │ A-A │ Reflective, subdued │
│ │ (plag.) │ │ (below) │ │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 3 │ Phrygian│ E │ E-E │ Mystical, intense │
│ │ (auth.) │ │ │ │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 4 │ Phrygian│ E │ B-B │ Penitential, dark │
│ │ (plag.) │ │ │ │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 5 │ Lydian │ F │ F-F │ Joyful, bright │
│ │ (auth.) │ │ │ (avoids B♮-F tritone│
│ │ │ │ │ with B♭) │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 6 │ Lydian │ F │ C-C │ Gentle, pastoral │
│ │ (plag.) │ │ │ │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 7 │ Mixolyd.│ G │ G-G │ Triumphant, regal │
│ │ (auth.) │ │ │ │
├──────┼─────────┼────────────┼──────────┼─────────────────────┤
│ 8 │ Mixolyd.│ G │ D-D │ Warm, contemplative │
│ │ (plag.) │ │ │ │
└──────┴─────────┴────────────┴──────────┴─────────────────────┘
Hildegard's Modal Preferences:
- Mode 1 (Dorian authentic): Most common — used for Marian texts, visions,
theological depth
- Mode 5 (Lydian authentic): Second most common — for joyful, celebratory texts
(Trinity, angels, saints)
- Mode 3 (Phrygian): Rare but striking — for penitential or mystical intensity
- Plagal modes: Less common in Hildegard; she prefers wide, soaring melodies
that require authentic (higher) range
Modal Selection by Liturgical Context:
- Marian feasts → Mode 1 (Dorian)
- Trinity, angels → Mode 5 (Lydian) or Mode 7 (Mixolydian)
- Penitential seasons (Lent) → Mode 4 (Phrygian plagal)
- General saints → Mode 1 or Mode 8
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 · 333 lines · 108 tokens per session scan A c654571db8f7
compose-sacred-music is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 4d ago), licensed MIT. It adds 108 tokens to every session and 4,058 once invoked, about $0.0004 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-03.
Other skills, from other repositories
poteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
deliberate-ai-use
Bevisst KI-bruk i Nav: grønn og rød sone, tre-forsøks-regelen, erfaringsnivå og generer-så-forstå, med forskningen bak. Bruk når utvikleren spør om KI bør gjøre en oppgave, vil lære, eller når en oppgave skal plasseres i grønn eller rød sone.
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".
init-workspace
Adapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".
unit-lane
One-shot lane conductor for a delivery unit: triage, implement, evidence, and close in a single document. Triggers: "unit-lane", "run the lane", "work on this feature/fix", "build this unit".