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 appraise-gemstonegit 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/appraise-gemstone)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/appraise-gemstone"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/appraise-gemstone/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/appraise-gemstone"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/appraise-gemstone.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.00088 | $0.04093 |
| Opus 5 | $0.00044 | $0.02047 |
| Sonnet 5 | $0.00018 | $0.00819 |
| Haiku 4.5 | $0.00009 | $0.00409 |
Grade A, and why
appraise-gemstone 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 6d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Appraise Gemstone
Appraise gemstone value using the four Cs (colour, clarity, cut, carat weight), treatment detection, origin assessment, and market factor analysis. This is educational advisory guidance only and does not constitute a certified gemological appraisal.
DISCLAIMER: This procedure provides educational guidance on gemstone valuation methodology. It is NOT a certified appraisal. For insurance, estate, sale, or legal purposes, always obtain a formal appraisal from a certified gemologist (GIA Graduate Gemologist, FGA, or equivalent). Gemstone values can vary enormously based on factors that require hands-on professional assessment.
When to Use
- You want to understand the factors that determine a gemstone's value
- You are pre-screening stones before paying for a professional appraisal
- You need to evaluate whether a seller's asking price is within a reasonable range
- You are learning gemstone grading methodology for educational purposes
- You want to understand how treatment status affects value
Inputs
- Required: Identified gemstone (species confirmed — see
identify-gemstone) - Required: Access to the stone (loose preferred; mounted stones limit assessment)
- Optional: Carat scale (accurate to 0.01 ct)
- Optional: 10x loupe or gemological microscope
- Optional: Daylight-equivalent light source (5500-6500K)
- Optional: Colour grading master stones or reference images (GIA system)
- Optional: Refractometer and Chelsea filter (for treatment detection)
Procedure
Step 1: Colour Grading
Assess the stone's colour using the three components: hue, saturation, and tone.
Colour Assessment Framework:
HUE: The dominant spectral colour
+------------------+------------------------------------------+
| Primary Hue | Examples |
+------------------+------------------------------------------+
| Red | Ruby, red spinel, pyrope garnet |
| Orange | Spessartine garnet, fire opal |
| Yellow | Yellow sapphire, citrine, chrysoberyl |
| Green | Emerald, tsavorite, peridot, tourmaline |
| Blue | Sapphire, aquamarine, tanzanite |
| Violet/Purple | Amethyst, purple sapphire |
| Pink | Pink sapphire, morganite, kunzite |
+------------------+------------------------------------------+
Secondary modifiers: yellowish-green, purplish-red, orangy-pink, etc.
SATURATION: Intensity of the colour
+------------------+------------------------------------------+
| Level | Description |
+------------------+------------------------------------------+
| Vivid | Pure, intense colour (most valuable) |
| Strong | Rich colour, slight modifier |
| Moderate | Noticeable colour, some grey/brown |
| Weak | Faint colour, significant grey/brown |
| Greyish/Brownish | Colour masked by grey or brown modifiers |
+------------------+------------------------------------------+
TONE: Lightness or darkness
+------------------+------------------------------------------+
| Level | Description |
+------------------+------------------------------------------+
| Very light | Pastel, may lack presence |
| Light | Attractive in some species (aquamarine) |
| Medium-light | Often ideal for many species |
| Medium | Classic "fine" tone for most coloured |
| | gemstones |
| Medium-dark | Rich, but watch for over-darkening |
| Dark | Colour may appear black face-up |
| Very dark | Loses transparency, appears opaque |
+------------------+------------------------------------------+
IDEAL COLOUR RANGES (highest value):
- Ruby: medium-dark, vivid red ("pigeon blood")
- Sapphire: medium, vivid blue (not too dark, not violetish)
- Emerald: medium, vivid green (not yellowish, not bluish)
- Tanzanite: medium-dark, vivid violetish-blue
- Aquamarine: medium, strong blue (not greenish)
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.
- 6d ago First seen · 365 lines · 88 tokens per session scan A 478071310d9a
appraise-gemstone is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 4,093 once invoked, about $0.0004 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…
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".
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".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…