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 consult-natural-historygit 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/consult-natural-history)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/consult-natural-history"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/consult-natural-history/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/consult-natural-history"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/consult-natural-history.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.00102 | $0.04376 |
| Opus 5 | $0.00051 | $0.02188 |
| Sonnet 5 | $0.00020 | $0.00875 |
| Haiku 4.5 | $0.00010 | $0.00438 |
Grade A, and why
consult-natural-history 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 9d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consult Natural History
Reference Hildegard von Bingen's Physica for natural history knowledge — properties of plants, stones, animals, fish, birds, elements, and trees with their medicinal, symbolic, and practical applications.
When to Use
- You need to understand a specific plant, stone, or animal from Hildegard's perspective
- You want to explore symbolic or medicinal properties of natural objects in Physica
- You are researching medieval natural history and cosmology
- You need to cross-reference properties across categories (e.g., a plant and a stone with similar temperament)
- You want to integrate Physica's knowledge into health, spiritual, or creative practice
- You are studying the relationship between nature and theology in Hildegard's thought
Inputs
- Required: Category to consult (plants, stones, animals, fish, birds, elements, trees, reptiles, metals)
- Required: Specific item or property inquiry (e.g., "emerald", "fennel", "properties of fire element")
- Optional: Application context (medicinal, symbolic, liturgical, practical)
- Optional: Related temperament or ailment (to guide property interpretation)
- Optional: Cross-reference request (e.g., "plants and stones for cold temperament")
Procedure
Step 1: Identify the Category in Physica
Determine which of the nine books of Physica contains the requested knowledge.
Physica — Nine Books of Natural History:
┌──────┬────────────────┬──────────────┬─────────────────────────┐
│ Book │ Title │ # Entries │ Focus │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ I │ PLANTS │ 230 entries │ Herbs, grains, spices, │
│ │ (Plantae) │ │ vegetables — medicinal │
│ │ │ │ and dietary properties │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ II │ ELEMENTS │ 7 entries │ Fire, air, water, earth,│
│ │ (Elementa) │ │ wind, stars, sun/moon │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ III │ TREES │ 27 entries │ Oak, apple, willow, │
│ │ (Arbores) │ │ birch — wood, fruit, │
│ │ │ │ leaves, symbolic meaning│
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ IV │ STONES │ 26 entries │ Gems and minerals — │
│ │ (Lapides) │ │ healing, protection, │
│ │ │ │ spiritual properties │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ V │ FISH │ 37 entries │ Freshwater & saltwater │
│ │ (Pisces) │ │ fish — dietary guidance │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ VI │ BIRDS │ 72 entries │ Domestic & wild birds — │
│ │ (Aves) │ │ meat properties, eggs, │
│ │ │ │ symbolic meanings │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ VII │ ANIMALS │ 45 entries │ Mammals — domestic & │
│ │ (Animalia) │ │ wild, medicinal uses of │
│ │ │ │ parts (bones, organs) │
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ VIII │ REPTILES │ 16 entries │ Snakes, frogs, worms — │
│ │ (Reptilia) │ │ medicinal (external) and│
│ │ │ │ symbolic (often negative│
├──────┼────────────────┼──────────────┼─────────────────────────┤
│ IX │ METALS │ 8 entries │ Gold, silver, iron, │
│ │ (Metalla) │ │ copper — practical and │
│ │ │ │ medicinal applications │
└──────┴────────────────┴──────────────┴─────────────────────────┘
Lookup Process:
1. Identify which category the inquiry falls under
2. Locate the entry within that book (alphabetical or grouped by type)
3. Extract properties: temperature, moisture, medicinal use, contraindications
4. Note symbolic or theological associations if relevant
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.
- 9d ago First seen · 360 lines · 102 tokens per session scan A a00a73b0b549
consult-natural-history is a skill published in the GitHub repository pjt222/agent-almanac (33 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 4,376 once invoked, about $0.0005 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.
Other skills, from other repositories
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
astro-dso-doc
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".