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 cut-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/cut-gemstone)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/cut-gemstone"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/cut-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/cut-gemstone"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/cut-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.00093 | $0.03179 |
| Opus 5.5 | $0.00037 | $0.01272 |
| Sonnet 5.5 | $0.00019 | $0.00636 |
| Haiku 4.5 | $0.00009 | $0.00318 |
Grade A, and why
cut-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 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut Gemstone
Cut gemstones from rough material using cabochon and faceting techniques, including rough assessment, orientation planning, dopping, grinding, and faceting geometry.
When to Use
- You have rough gemstone material and want to cut it into a finished cabochon or faceted stone
- You need to plan cutting orientation for optimal colour, yield, or optical phenomena
- You are setting up a cabbing machine or faceting machine for the first time
- You want to understand crown and pavilion angles for standard brilliant cuts
- You need to select the appropriate cutting approach for a given material
Inputs
- Required: Rough gemstone material (identified species — see
identify-gemstone) - Required: Cutting approach decision: cabochon or faceting
- Required: Target shape and approximate size
- Optional: Trim saw with diamond blade
- Optional: Cabbing machine with 80/220/600/1200/3000 grit wheels (for cabochons)
- Optional: Faceting machine with index gear, mast, and lap set (for faceting)
- Optional: Dop wax or epoxy, dop sticks, alcohol lamp
- Optional: Templates (oval, round, marquise) in standard calibrated sizes
Procedure
Step 1: Rough Assessment and Safety Check
Evaluate the rough material before any cutting begins.
Rough Assessment Checklist:
+--------------------+------------------------------------------+
| Factor | Assessment |
+--------------------+------------------------------------------+
| Species | Identified? (MANDATORY before cutting) |
| | Toxic dust risk? (check below) |
+--------------------+------------------------------------------+
| Fractures | Internal fractures that limit yield? |
| | Will the stone break during cutting? |
+--------------------+------------------------------------------+
| Colour zones | Where is the best colour concentrated? |
| | Can the cut centre the colour? |
+--------------------+------------------------------------------+
| Inclusions | Large inclusions that should be cut away?|
| | Silk for star stones? (orient for star) |
+--------------------+------------------------------------------+
| Size and shape | What finished shapes fit this rough? |
| | Calibrated size possible? |
+--------------------+------------------------------------------+
| Yield estimate | Approximate finished weight as % of rough|
| | Typical: 25-40% for faceting |
| | Typical: 40-60% for cabochons |
+--------------------+------------------------------------------+
SAFETY — TOXIC DUST MATERIALS:
These minerals produce hazardous dust when cut. Use wet cutting ONLY,
ensure ventilation, and wear an appropriate respirator:
- Chrysotile (asbestos serpentine) — NEVER cut dry
- Malachite — copper carbonate dust is toxic
- Cinnabar — mercury sulfide, extremely toxic
- Orpiment/Realgar — arsenic compounds
- Chrysocolla — copper silicate, moderate risk
- Tiger's eye (fibrous) — fine silica fibers
ALL stone cutting produces silica dust. Always use water cooling
and never grind or cut dry without a dust extraction system.
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 · 275 lines · 93 tokens per session scan A 6d02fb201b73
cut-gemstone is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 3,179 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
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".
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".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling; it owns the repo-wide bug hunt, security research, and broken-version investigation (scoped and budgeted per dimension, as distinct from review-change's change-scoped review). Persist one severity-ranked, F-numbered report with…
review-change
Review a change with only applicable internal axes, classify every finding, persist fix-now work, and return one evidence-backed decision. Findings only; --adversarial N uses isolated reviewers; --synthesize fuses supplied reviewer tables. Triggers: "review-change", "review this change", "adversarial review".