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 collect-preserve-specimensgit 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/collect-preserve-specimens)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/collect-preserve-specimens"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/collect-preserve-specimens/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/collect-preserve-specimens"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/collect-preserve-specimens.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.00139 | $0.05316 |
| Opus 5 | $0.00069 | $0.02658 |
| Sonnet 5 | $0.00028 | $0.01063 |
| Haiku 4.5 | $0.00014 | $0.00532 |
Grade A, and why
collect-preserve-specimens 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 8d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collect and Preserve Specimens
Collect and preserve insect specimens to museum-grade standards for taxonomic study, reference collections, and ecological research.
When to Use
- You need physical specimens for definitive taxonomic identification
- You are building a reference collection for a habitat, region, or taxon
- You are preserving voucher specimens for published ecological research
- You need to send specimens to taxonomic specialists for identification
- You are curating or restoring an existing insect collection
Inputs
- Required: Legal authorization to collect at the intended site (permits, landowner consent)
- Required: Collection equipment appropriate to the target taxa
- Required: Preservation materials (pins, ethanol, or both)
- Required: Labeling materials (archival paper, fine-point pen or printer)
- Optional: Spreading boards for Lepidoptera and Odonata
- Optional: Relaxing chamber for rehydrating dried specimens
- Optional: Dissecting microscope for sorting and preparation
- Optional: Database or catalog system for specimen records
- Optional: Unit trays, drawers, and storage cabinets
Procedure
Step 1: Verify Legal Requirements
Before any collection activity, confirm that you have the legal right to collect at the site and that your target taxa are not protected.
FUNDAMENTAL RULE:
Never collect without proper authorization. Never collect from
protected areas without explicit permits. Never collect protected
species. The scientific value of a specimen is zero if it was
collected illegally — it cannot be published, deposited in a
museum, or used in formal research.
Legal Checklist:
+--------------------+------------------------------------------+
| Requirement | Verify |
+--------------------+------------------------------------------+
| Land access | Written permission from landowner, or |
| | site is publicly accessible for |
| | collecting (many parks prohibit it) |
+--------------------+------------------------------------------+
| Collection permit | Required for most public lands, nature |
| | reserves, national parks. Apply through |
| | the managing agency. Specify taxa, |
| | methods, dates, and quantities. |
+--------------------+------------------------------------------+
| Protected species | Check national and regional red lists, |
| | CITES appendices, and local endangered |
| | species legislation. Some butterflies, |
| | beetles, and dragonflies are protected. |
+--------------------+------------------------------------------+
| Export/import | Moving specimens across international |
| | borders requires phytosanitary |
| | certificates and may require CITES |
| | permits depending on the taxon. |
+--------------------+------------------------------------------+
| Institutional | If collecting for an institution, follow |
| protocols | their collection policy and ethics |
| | review requirements. |
+--------------------+------------------------------------------+
Minimizing Collection Impact:
- Collect only the minimum number of specimens needed
- Avoid collecting from small or isolated populations
- Do not collect gravid (egg-bearing) females if population is small
- Record the abundance at the site — if the species appears rare, photograph instead
- Prefer common and abundant species for teaching collections
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.
- 8d ago First seen · 447 lines · 139 tokens per session scan A ee524594e094
collect-preserve-specimens is a skill published in the GitHub repository pjt222/agent-almanac (33 stars, last pushed yesterday), licensed MIT. It adds 139 tokens to every session and 5,316 once invoked, about $0.0007 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…
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".
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".
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".
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".